Publish: Cascading version update

[Marius Storhaug (MariusStorhaug)]

Change

Main functionality changes:

• Added ability to do cascading updates to "latest" versions for major and major.minor for Template Specs and Bicep Registry. This will allow consumers to specify a major, or major.minor version in the template reference. i.e.:
  • br:acr.azurecr.io/bicep/modules/microsoft.storage.storageaccount:1 to always get the latest non-breaking changes (features and patches/fixes) to their deployment,
  • br:acr.azurecr.io/bicep/modules/microsoft.storage.storageaccount:1.2 to only get the latest patches for their module reference, this in addition to the already able way with
  • br:acr.azurecr.io/bicep/modules/microsoft.storage.storageaccount:1.2.123 for a specific version.

Get-ModulesToUpdate

• Rename script and functions from *Update -> *Publish to align better with its usage.
• Reduce verbose logging where this was more noise than helpful

Pipelines:

• Storage Account | ADO
• 
• 

Know issues:

Running the pipelines in ADO for a given module multiple times on the same commit will fail for the publishing step as it will attempt to publish a package using the same version which is not supported for ADO Universal Packages.

Type of Change

Please delete options that are not relevant.

• Bug fix (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)
• This change requires a documentation update (Wiki)

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

[Marius Storhaug (MariusStorhaug)]

Ready for review