Pods logs at the default log level should make it easier to debug Supervisor ingress, SNI, and TLS certificate problems

[cfryanr]

Is your feature request related to a problem? Please describe.

When the Supervisor's configuration has bad TLS certs, missing TLS certs, bad or missing incoming SNI information on requests, or other problems related to driving https traffic into the Supervisor pods, then the pod logs should contain helpful hints, even when at the default log level.

Describe the solution you'd like

Today, many of the helpful log statements are at the debug or trace level. Add more statements at the default level, or change some of the existing statements to be visible at the debug level. Make sure that at the default level there is not too much logging, and no sharing of sensitive information like request query params, etc.

Using only the default log level, an admin user should be able to tell:

• Are the default and per-FederationDomain certificates being loaded without error?
• On each incoming request, which certificate is being used, and why? Show the request path in so you can tell with which request the log statement corresponds.

Describe alternatives you've considered

None.

Are you considering submitting a PR for this feature?

• How will this project improvement be tested?
• How does this change the current architecture?
• How will this change be backwards compatible?
• How will this feature be documented?

This could be documented in https://pinniped.dev/docs/howto/configure-supervisor/, which could have a new troubleshooting section. It could also mention that when using an Ingress, make sure that the Ingress will pass the SNI information through to the Supervisor.

Additional context

None.

[cfryanr]

This is already needed with a single FederationDomain, but note that this is also closely related to #1406, because making this easier to debug will be even more needed with multiple FederationDomains.