Filter unauthorized views in InformationSchema

[jon-wei]

This PR adjusts the InformationSchema class such that it properly filters out views based on authorization checks. Previously it checked the view subschema against the "druid" schema name, and thus fell back on the unfiltered path.

This PR has:

• been self-reviewed.
• added documentation for new or modified features or behaviors.
• 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.

[clintropolis]

I guess NamedViewSchema should probably use this injected name instead of its own name, and also SqlResourceCollectorShuttle should probably accept it as well since it does for druid schema name.

[jon-wei]

It would take some additional changes in DruidPlanner and beyond to support passing in the view name, so I decided to just use a fixed name for the view schema, I don't think the additional complexity is worth it currently.