Introduce resource_metadata parameter resolver for BearerTokenAuthenticationEntryPoint

[Kehrlann]

Dynamically the resource_metadata from the incoming HTTP request in BearerTokenAuthenticationEntryPoint. This is required when you want to, say, preserve the path parameter of the incoming request, or include a query string.

See [RFC 9728 > 3.1. Protected Resource Metadata Request](https://datatracker.ietf.org/doc/html/rfc9728#section-3.1

If the resource identifier value contains a path or query component, any terminating slash (/) following the host component MUST be removed before inserting /.well-known/ and the well-known URI path suffix between the host component and the path and/or query components. The consumer of the metadata would make the following request when the resource identifier is https://resource.example.com/resource1 and the well-known URI path suffix is oauth-protected-resource to obtain the metadata, since the resource identifier contains a path component:

GET /.well-known/oauth-protected-resource/resource1 HTTP/1.1
Host: resource.example.com

Using path components enables supporting multiple resources per host. This is required in some multi-tenant hosting configurations.