[7º] - Release/v2.0.0 authorization: Enabled BPN block and Role Authorization in the Digitla

[matbmoser]

Why we create this PR?

There is the requirement to block the user when the token configuration is not correct and authorized. We need to block if the configuration is enabled the users that have different bpns as in the authorization configuration.

The requirement is because of data souverenity, and makes the app comply into the guidelines of authorization and authentication. Also is important to improve the backend configuration and security, as well as the backend.

What we want to achieve with this PR?

Implement the authorization for BPN and AppId Authentication.
Improve the security configuration in the backend and frontend.

What is new?

Added

• Added Check of BPN Number in Frontend (With Trigger in Configuration)
• Added Check of BPN Number in Backend (With Trigger in Configuration)
• Added Check for appId Roles in Frontend (With Trigger in Configuration)
• Added Check for appId Roles in Backend (With Trigger in Configuration)
• Added new security checks in the backend and frontend
• Added new non authorized view in the frontend

Update

• Refactored helm chart values configuration.
• Refactored backend values chart configuration

PR Linked to:

Tickets
CMP-747]

[saudkhan116]

I reviewed this PR and the changed files are compliant.