Improve logging

• add access log
• Fix startup debug log. On startup, AA currently logs:

Jan 28 14:09:14 docker1.prd.ams.surfconext.nl aaserver[831]: 2026-01-28 13:09:14,018  INFO [main] aa.config.AuthorityResolver:31 - Parsed file:///attributeAuthorities.yml with configuration AuthorityConfiguration(authorities=[aa.model.AttributeAuthorityConfiguration@6518436, aa.model.AttributeAuthorityConfiguration@375299, aa.model.AttributeAuthorityConfiguration@bf8a9da0, aa.model.AttributeAuthorityConfiguration@5be7f8c, aa.model.AttributeAuthorityConfiguration@b9722f44, aa.model.AttributeAuthorityConfiguration@6e8d0de3, aa.model.AttributeAuthorityConfiguration@3529a5f3])

This doesn't tell me anything. Instead, dump the config of each of the authorities it has configured, so that I can check if that matches the input config.

• [] If an exception occurs while processing a request or response, log the full offending request/reponse. For example:

Apr  2 09:23:52 docker4.prd.utr.surfconext.nl aaserver[818]: 2026-04-02 07:23:52,376  WARN [http-nio-8080-exec-19] o.s.w.s.m.s.DefaultHandlerExceptionResolver:254 - Resolved [org.springframework.http.converter.HttpMessageNotReadableException: JSON parse error: Cannot deserialize value of type `java.util.ArrayList<java.lang.String>` from Object value (token `JsonToken.START_OBJECT`)]

Start by locating the AuthorityResolver startup logging and the request/response exception-handling paths. Compare the current startup message with the configured authority data, then identify how access logs and offending requests or responses can be emitted. Done means all three requested logging improvements are covered and their output is useful for diagnosing configuration and processing failures.