[Pipeline] Users/seseicht/adjust publish

[SeSeicht]

Description

#1085

These change will allow to publish the artifacts in a different subscripion than the validation modules.

Pipeline references

For module/pipeline changes, please create and attach the status badge of your successful run.

Pipeline

Type of Change

Please delete options that are not relevant.

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Update to documentation

Checklist

• I'm sure there are no other open Pull Requests for the same update/change
• My corresponding pipelines / checks run clean and green without any errors or warnings
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (readme)
• I did format my code

[eriqua]

Thanks a lot for introducing this new feature, very much needed. A couple of comments from my side:

1. Discuss if the same SP should have permissions on both validation and publish subscription or if we need to support 2 different SP/serviceConnections as well. This is often the case with customers requiring an SP to be mapped to a specific subscription
2. If going with supporting 2 SP this PR will closely relate to PR #1452 (see also comment to issue #1465)
3. Additional documentation needed and depending on the 2 points above

[eriqua]

Converted to draft to be merged after publishing the next release and after team agreement on all secret names

[MariusStorhaug]

Merging to a full implementation branch for 'overhauling' authentication