feat: resolve extension parameters in compiler passes

[Ocarthon]

1. Why is this change necessary?

CompilerPassConfigTrait is used in some shopware compiler passes to read the configuration of the framework extension. The problem is, that parameters (e.g. '%env(DUMMY_ENV)%') will not get resolved. If the Symfony configuration class requires specific types, they may not be satisfied without the resolved values. This will lead to a crash of the kernel.

2. What does this change do, exactly?

Before processing the extension config values in shopware compiler passes, resolve the parameters.

3. Describe each step to reproduce the issue or behaviour.

• Put the following into config/packages/messenger.yaml

framework:
   messenger:
       transports:
           test:
               dsn: ''
               retry_strategy:
                   max_retries: '%env(int:DUMMY_ENV_VAR)%'

• Run bin/console -> Kernel will fail to start with the error Invalid type for path "framework.messenger.transports.test.retry_strategy.max_retries". Expected "int", but got "string".

4. Please link to the relevant issues (if any).

5. Checklist

• I have rebased my changes to remove merge conflicts
• I have written tests and verified that they fail without my change
• I have created a changelog file with all necessary information about my changes
• I have written or adjusted the documentation according to my changes
• This change has comments for package types, values, functions, and non-obvious lines of code
• I have read the contribution requirements and fulfil them.

[CLAassistant]

All committers have signed the CLA.

[Ocarthon]

Note also that this also concerns shopware 6.5.8.X.

[suchmaske]

I just ran into exactly that issue when trying to upgrade a Shopware project from 6.5.5.x to 6.5.8.x

[shyim]

We will backport it also too 6.5.x

[Ocarthon]

I also now added a minimal test case for validation.