Add OIDC clientName property

[sberyozkin]

This simple PR adds an optional OIDC client name property.

If set, it is expected to provide a nice, human readable description of the registered client/application.
Typically, with social providers or Keycloak, when we register applications, Description is what this client name property represents.

As far as an immediate impact on Quarkus OIDC is concerned, it is only about logging a client name in a couple of places for now, if it is set. Users can also access it when creating Qute templates for creating HTMLs for interacting with users.

It is also relevant for the OIDC Dynamic client registration work which is underway now (see the client_name in https://openid.net/specs/openid-connect-registration-1_0.html#ClientMetadata and https://openid.net/specs/openid-connect-registration-1_0.html#RegistrationRequest), so when the OIDC client is registered automatically, Quarkus will set quarkus.oidc.client-name itself, etc

CC @calvernaz

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit b482750.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.