Add krakend backend integration for sonar/deptrack widgets consuming

[callmevladik]

Portal UI should consume widgets information based on the Krakend ingress URL endpoint. The portal should pass the Authorization token from the portal. The portal should use the following endpoints:

SonarQube widget: https://api.eks-sandbox.aws.main.edp.projects.epam.com/widgets/sonarqube/measures/component?component=demo&metricKeys=bugs,code_smells
Dependency track: https://api.eks-sandbox.aws.main.edp.projects.epam.com/widgets/deptrack/project?name=demo
Acceptance Criteria
Portal UI is updated to consume widgets information via the Krakend ingress URL.
The Authorization token is correctly passed from the portal to the Krakend endpoints.
SonarQube widget information is correctly fetched using the endpoint /widgets/measures/component with the existing query string.
Dependency track information is correctly fetched using the endpoint /widgets/deptrack/project with the existing query string.
All endpoints are tested to ensure they return the correct data.
Implementation Plan

1. Update Portal UI Configuration:

Modify the Portal UI to use the Krakend ingress URL endpoints for fetching widgets information.
Ensure the Authorization token is passed correctly from the portal.

2. Integrate with SonarQube Widget Endpoint:

Update the Portal UI to fetch SonarQube widget information from /widgets/measures/component.
Ensure the existing query string is preserved and used correctly.

3. Integrate with Dependency Track Endpoint:

Update the Portal UI to fetch dependency track information from /widgets/deptrack/project.
Ensure the existing query string is preserved and used correctly.

4. Testing and Verification:

Perform comprehensive testing to verify that the Portal UI correctly consumes the widgets information from the specified endpoints.
Ensure that the Authorization token is passed and that the data returned is accurate.
Fix any issues identified during the testing phase.