[drgrice1]

Content generators and the login status template fetched the authenticated user's record from the database again even though it is already cached in $c->authen->{user}. Use the cached record instead, and keep it current when the LTI modules or the Options and UserList pages update that user. Since the cached user always exists in Feedback and GatewayQuiz, the checks for a missing user there are removed. Also preserve showOldAnswers when an LTI login updates a user's data.

Validate and cache the effective user during dispatch. The effective user was not validated until the login status template was rendered, and content generators fetched the effective user's record from the database again. Now WeBWorK::dispatch validates the effective user, falls back to the real user if it does not exist, and caches the record in $c->authen->{effective_user}. Use that cached record everywhere instead, and remove the checks for a missing effective user that are no longer needed.

Remove the unused permission level argument from the GatewayQuiz "can" methods. The permission level was fetched from the database and passed to all of the "can" methods, but none of them used it.