Signal rejection to clients when providing a query parameter that has no effect on an endpoint

When a client is passed a query parameter into an endpoint that has no effect (it would otherwise be ignored) we should reject in order to let the client know the passed query parameter is not supported on the provided endpoint.

Something like a `CustomRejection` that is `UnsuportedQueryParameterRejection`.

This will help clients to know what is supported and not on a certain API endpoint.

No file, test, or entry point is identified in the issue. Start by locating endpoint query-parameter parsing and the existing rejection handling, then trace how unsupported parameters are currently ignored. Done means an endpoint rejects an ineffective query parameter with a clearly named unsupported-parameter rejection and clients can distinguish it from other failures.

Written by the indexing model from the issue text.