Add automation to keep the provider build workflows up to date

[ringods]

How a provider needs to be build, packaged and released is mainly defined by Pulumi. They also have a lot of automation for keeping the Github Actions workflows up to date in all of the provider repositories.

We could benefit from having an automated setup serving two purposes:

• initial setup of the workflows for new providers being set up in Pulumiverse
• updating the workflows to support new features coming from Pulumi (e.g recent addition was support for Java)

Pulumi is aware that building & releasing a provider must become must simpler. There is planned work to make the pulumi/ci-mgmt a consumable artefact. This artefact, with the proper configuration, would be able to generate the correct workflows for a provider repository.

Let's follow up on that work, test it, provide feedback (issues & PR), so we can build on top of that effort.

[ringods]

I'm making progress on this one. The following providers serve as a testbed for the automatic workflow generation, driven by pulumi/ci-mgmt:

• https://github.com/pulumiverse/pulumi-acme
• https://github.com/pulumiverse/pulumi-matchbox

[omercnet]

happy to include pulumi-vercel in this testing

[ringods]

@omercnet I will notify you to get included. This PR first needs to be merged:

pulumi/ci-mgmt#1099

This also changes the permission model for Pulumi-managed providers, so the team needs to review and test these changes more thorougly.

If this is merged, I have another set of changes lined up to make the upgrade-provider and upgrade-bridge workflows going for third-party packages.

[omercnet]

I'm already using upgrade provider and most of the ci-mgmt in https://github.com/pulumiverse/pulumi-vercel and https://github.com/descope/pulumi-descope/

let me know if you need any assistance - I'd love to see this work seamlessly

[tmeckel]

Related to #298