Register composed-email scope on Maskinporten client for TT02 and PROD

[Ahmed-Ghanam]

Description

The k6 tests for the composed-email endpoint (orders-composed-email-v2.js) fail in TT02 and PROD because the Maskinporten client used by the test runner does not have the required scope.

The scope altinn:serviceowner/notifications.composedemail.create must be registered on the Maskinporten client (mpClientId) in both environments.

The composed-email test steps have been temporarily disabled in the TT02 and PROD workflows and must be re-enabled after the scope is registered.

All AT environments (AT22, AT23, AT24) pass since they use the token generator for authentication instead of Maskinporten.

Related: #1756, #1814

Steps

• Register scope altinn:serviceowner/notifications.composedemail.create on the Maskinporten client in TT02 (Samarbeidsportalen)
• Register scope altinn:serviceowner/notifications.composedemail.create on the Maskinporten client in PROD (Samarbeidsportalen)
• Re-enable composed-email test step in use-case-TT02.yaml
• Re-enable composed-email test step in use-case-PROD.yaml
• Re-enable composed-email test step in regression-test-TT02.yaml
• Re-enable composed-email test step in regression-test-PROD.yaml
• Re-run TT02 and PROD workflows to verify