chore: Modified bug issue template to add checkbox to report potential regression.

[ashishdhingra]

Issue

Issue number, if available, prefixed with "#"

Description

• Modified bug issue template to add checkbox to report potential regression.
• Added GitHub action to add/remove label potential-regression when issue is created/edited.

NOTE:

• The GitHub action code was ported from CDK repo.
• The label potential-regression would need to be created manually (we could use color #FF6700 and description Marking this issue as a potential regression to be checked by team member to make it consistent across SDK repos)

Label potential-regression would make issue standout in the list and help engineers to handle high severity issues effectively.

Testing

How was this change tested?

Additional context

Add any other context about the PR here.

Checklist

• If you wrote E2E tests, are they resilient to concurrent I/O?
• If adding new public functions, did you add the @public tag and enable doc generation on the package?

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[kuhe]

this should probably say that differences from AWS SDK for JavaScript v2 are not regressions

[ashishdhingra]

this should probably say that differences from AWS SDK for JavaScript v2 are not regressions

@kuhe Thanks for the feedback. However, the purpose of this checkbox is to identify potential regression in the current major version of SDK, not differences between previous and current major version. The change is implemented across all SDK(s), JS v3 one if them.

Context: There was a regression issue in CDK and team implemented this checkbox along with GitHub action that adds potential-regression label. It was helpful in triaging such issues quickly and has assisted in identifying some regression issues till date. There is another PR for JS v2. Even though that's getting deprecated, any future security issue fixes or service updates could also cause a regression. Hence I had reopened that PR; @aBurmeseDev will discuss it with JS team.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.