feat: Client tests using Example app

[dstenroejl]

Description

• Classes that we will refactor/move in another PR has been renamed and prefixed with Obsolete.
• Added DisableTestParallelization to disable test parallelization because we have to set of apps (Process Manager + Orchestrations; Process Manager + Example Orchestrations) and their tests cannot run in parallel.
• Implemented tests in ProcessManager.Client.Tests that uses the Example app to test the framework through the Client.
• Implemented tests in Example.Orchestrations.Tests that uses the Example app to test the framework through the Api.

References

Link to assignment: https://app.zenhub.com/workspaces/mosaic-60a6105157304f00119be86e/issues/gh/energinet-datahub/team-mosaic/424

Checklist

• Should the change be behind a feature flag?
• Can the feature be meaningfully disabled or circumvented if there are issues (e.g., database-breaking changes)?
• Has it been considered whether data is being delivered to the wrong actor?
• Subsystem test executed (dev_002/dev_003)
• Is there time to monitor state of the release to Production?
• Reference to the task

[github-actions]

Test results for \source\ProcessManager.Client.Tests\bin\Release\net8.0\Energinet.DataHub.ProcessManager.Client.Tests.dll

10 tests   10 ✅  3m 6s ⏱️
 1 suites   0 💤
 1 files     0 ❌

Results for commit c37ee92.

♻️ This comment has been updated with latest results.