Consider adding a `USER_FACING_<MODEL>_NAME` to each view model

[bencap]

We use such a model name in many places across the application, so having a global for each model name would greatly simplify the refactoring pain of changing model names. Of course, such a change would in itself be a great refactoring pain.

[bencap]

Thinking back on this, we could also add some internal property _core_class_name or something like that to each base view model. Then we can use that name everywhere we throw errors for the class (maybe this exists in conjunction with a global property, so that we don't need to import it when we are working with the classes but can still access it without a class instance if needed).