Make Actuator endpoint metrics distinguishable

When querying metrics, I would like to be able to query metrics related to endpoints (http.server.requests) such that I can filter out non-user facing endpoints like the Actuator endpoints. When monitoring, I want to look at things like request rate, error rate, and latency on user-facing endpoints, without access to the Actuator endpoints affecting those metrics.

If such filtering were possible, it could be used in excluding Actuator endpoints from alerts and graphs and ad hoc queries, when desired.

Some metrics backends may allow querying with wildcards/regex to approximate this. For example, in PromQL, the 5m request rate excluding Actuator endpoints might be written like this:

rate(http_server_requests_seconds_count{uri !~ "/actuator.*"}[5m])

But for a query like above to work, it would require all applications use the same management context-path. Having a simpler, more robust way to filter via a tag would be helpful.

/CC @jkschneider

The issue centers on http.server.requests and Actuator endpoints; start by tracing how Spring Boot exposes and tags these metrics and how the management context path is represented. Compare the requested tag-based filtering with the PromQL example; done means users can exclude Actuator traffic without relying on a shared context path.