E2E Testing | Change to umbrella env where possible

[evegufy]

Description

The basic idea is to adapt the existing workflow that executes the test automation (or create an additional workflow) to rump up the necessary components from the umbrella env and to execute the e2e tests against those components instead of some managed environment (like consortia dev or int env).

At this point in time, the following components are integrated in the umbrella chart (integration and enabling is ongoing):

• portal
• iam
• discoveryfinder
• bpndiscovery
• sdfactory
• miw

Acceptance Criteria

• Identify for which test cases the usage of the umbrella env might already be possible
• Change to umbrella env where possible

Relates to:

#441 (mock Clearinghouse)
eclipse-tractusx/sig-release#418

Benefits

Being able to e2e test interface dependencies in an automated manner without being reliant on a managed environments as this reliance isn't sustainable.