Add more log statements for authorization

[adarshsanjeev]

Adds logging and for the case that an exception is thrown during authorization

---

This PR has:

• been self-reviewed.
  • using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)
• added documentation for new or modified features or behaviors.
• a release note entry in the PR description.
• added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
• added or updated version, license, or notice information in licenses.yaml
• added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
• added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
• added integration tests.
• been tested in a test Druid cluster.

[paul-rogers]

Why do we need this?

This code translates the unauthorized exception into a runtime exception, which will change the code flow. The desired flow is that we throw the unauthorized exception which is caught by a Jersey handler up the hander stack. (I seem to recall issues when I tried to intercept that error as you've done here.)

If we want to log auth errors, that would be the place. Else, in the SQL resource, we already log errors. And, the statement logs failures at the end of the query process.

As a result, this step seems unnecessary. What problem is this trying to solve?