Upgrade workflows create duplicate issues and pull requests

[guineveresaenger]

#1110 seems to have caused an identical issue to be created every time the upgrade workflow runs. When all of the automation succeeds without intervention, this is not a problem. But in cases where the upgrade needs manual assistance, we'll see the same issue created over and over:

If an issue already exists, we should not create another one.

Additionally, if an automated pull request is not merged same-day, an (identical, most likely) new one is opened:

[guineveresaenger]

More information:

• Upgrade terraform-provider-artifactory to v12.3.3 pulumi-artifactory#929 was not discovered or closed by Upgrade terraform-provider-artifactory to v12.3.3 pulumi-artifactory#930 - these were likely created in the same workflow and the PR should have closed the issue (but maybe the existence of older issues confused thigs?)

• Additionally, the duplicative pull requests did not auto-close when Upgrade terraform-provider-artifactory to v12.3.3 pulumi-artifactory#930 merged.

[guineveresaenger]

pulumi/pulumi-alicloud#829 on the other hand, closes all 3 identically-named issues.

The main fix here seems to be to not open duplicative issues or pull requests.

[danielrbradley]

This was an issue in upgrade-provider which was fixed with pulumi/upgrade-provider#287