Users with no matching Staff Model instance should be handled more elegantly

[profcturner]

Particularly with REMOTE_USER usage someone may be authenticated and even a user auto created for which there is no matching staff entry. This needs to be caught and handled.

Another example is an initially created superuser (but they won't use have a Staff user). This may mean that the most recent version is difficult to install out of the box.

[profcturner]

One possibility is a Custom Remote User handler.

See:
https://docs.djangoproject.com/en/3.2/howto/auth-remote-user/

and setting create_unknown_user to False

https://docs.djangoproject.com/en/3.2/ref/contrib/auth/

[profcturner]

For now, at least enhanced guidance is given in the error reporting. Further the context_processor has been fixed not to through a further error in reporting the missing staff object.

[profcturner]

I think this is good enough for what was intended for 2.1.1