upgrade-provider automation mistakenly mixes bridge and upstream upgrades

[t0yv0]

Noticed this in pulumi/pulumi-aws#4752

https://github.com/pulumi/ci-mgmt/blob/master/provider-ci/internal/pkg/templates/bridged-provider/.github/workflows/upgrade-provider.yml#L83

The code:

        run: upgrade-provider "${{ github.repository }}" --kind="all" --target-version="${{ steps.target_version.outputs.version }}" #{{ if .Config.javaGenVersion }}#--java-version="#{{ .Config.javaGenVersion }}#"#{{ end }}#

The --kind="all" flag is mixing bridge and upstream upgrades in a single change, which makes it harder to understand where changes are coming from and harder to bisect issues. Would it be possible to scope this to only upstream upgrades? And have a separate workflow handle upgrading the bridge