[Idea] Pass a new “doNotPerformUpgrade” setting to Run-AlPipeline

[ChrisBlankDe]

Idea Description

If the latest release of an app is no longer compatible with the current BC version, the pipeline fails because it cannot publish it to the container. However, we don’t want to do without the breaking change check either.
The doNotPerformUpgrade parameter of Run-AlPipeline would be a good option here. Unfortunately, there is no easy way to set this parameter from within AL-Go.

I suggest we introduce a new setting and pass it to the function.

Contribution (Optional)

• I would be open to contributing to this idea (implementation, documentation, testing, etc.)

[aholstrup1]

Feature was merged in #2297 and will ship with next AL-Go version.

Thank you for the contribution 🚀

[ChrisBlankDe]

@aholstrup1
Since we reverted this #2305 due to an missing settinginitialization im not sure on how we proceed with this.
Should i create a new PR where we revert the revert and add a bugfix?