Provider login/consent views do not read client_name correctly

[matteo-s]

The provider authz_request_view shows the client_organization_name to the user in the login page. It reads the name from the resolved metadata, and falls back to client_id.

spid-cie-oidc-django/spid_cie_oidc/provider/views/authz_request_view.py

Lines 202 to 204 in b7b28a8

	"client_organization_name": tc.metadata.get(
	"client_name", self.payload["client_id"]
	),

Same goes for consent

spid-cie-oidc-django/spid_cie_oidc/provider/views/consent_page_view.py

Lines 59 to 61 in b7b28a8

	"client_organization_name": tc.metadata.get(
	"client_name", session.client_id
	),

The client_name is always blank, because it is provided inside the openid_relying_party subsection.

something like this fixes the issue

        context = {
            "client_organization_name": tc.metadata.get(
                "openid_relying_party", {}).get("client_name", self.payload["client_id"]),

I'm also wondering whether displaying the client_name is the best approach here, given that we should have the proper organization_name inside the federation metadata, which is required for CIE/SPID RPs as per https://docs.italia.it/italia/spid/spid-cie-oidc-docs/it/versione-corrente/metadata_oidc_rp.html

[peppelinux]

it should be better to point to

metadata.federation_entity.organization_name
if any, or
metadata.openid_relying_party.organization_name
if any, or
metadata.openid_relying_party.client_name
if any, or
metadata.openid_relying_party.client_id

do you agree?
If yes and if you can, please provide a PR for this