Remove UPP loading redundancy

[srallen]

Package app-project and lib-classifier

Is your feature request related to a problem? Please describe.

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

The UPP is loaded and stored in both the project app and classifier library. This is redundant. The classifier only needs to know about the UPP to know if the tutorial has been seen before and to store those last seen dates.

Describe the solution you'd like

A clear and concise description of what you want to happen.

Proposed solution is that the project app just be responsible for the UPP since it is used for more features there. The classifier can take in two props: one for the tutorial last seen dates as well as a callback for updating the UPP if needed.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Another option would be to pass in a snapshot for the UPP and continue to have a copy of it in the classifier store. The UPP store can be refactored to only make a request for it if a snapshot isn't passed in to the classifier.

Additional context

Add any other context or screenshots about the feature request here.

[srallen]

Removing the UPP from the classifier will also mean that the UPP store in the project app will have to be updated to manage creating the UPP resource upon first visit of the classify page. Perhaps the callback for updating the last seen timestamp of the tutorial can manage this too?