feat(clearingHouse): Integrate the Tagus Release V2 Api

[tfjanjua]

Description

Integration of the v2 api from Gaia-X Tagus release in company onboarding clearing house.

Why

v1 will be retired as of March 2025. Any API v1 calls will fail with a 400 HTTP Status Code.

Issue

Ref: 1217

Checklist

• I have followed the contributing guidelines
• I have performed a self-review of my own code
• I have successfully tested my changes locally
• I have added tests that prove my changes work
• I have checked that new and existing tests pass locally with my changes
• I have commented my code, particularly in hard-to-understand areas

[Phil91]

@tfjanjua you didn't checked the I have successfully tested my changes locally was that on purpose? Is there a way to test if the changes are working with the new api before merging it?

[tfjanjua]

@tfjanjua you didn't checked the I have successfully tested my changes locally was that on purpose? Is there a way to test if the changes are working with the new api before merging it?

Hi @Phil91 , thanks for your feedback
Actually I already have tested changes on my local but clearing house cannot access my local as clearing house calls callback url to tell us the validation results but I wanted to test the callback url call also as changes involved in callback url as well so, we have deployed this change into one of our envs. so I could test if clearing house is also able to call callback url and we are also receiving the results and processing it also ... then I will mark this checkbox I have successfully tested my changes locally.

[ntruchsess]

I did move the implicit client-side formating from the query to the business-logic adjusting the respective model-classes and unit-tests.
please also see my new review comments (and pull my changes before proceeding)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud