chore(release): switch release workflow to have tag trigger

[charliedmcb]

Fixes #

Description Working towards a more automated release process. Removing the manual step of triggering with specified tag to automatic trigger based off tagging.

This is aligned behavior with the aws provider:

• https://github.com/aws/karpenter-provider-aws/blob/9e113aaca23bce17e99cd6f14447927e7c89e3d4/.github/workflows/release.yaml

How was this change tested? Nothing additional *

Does this change impact docs?

• [ ] Yes, PR includes docs updates
• [ ] Yes, issue opened: #
• [x] No

Release Note

NONE

[coveralls]

Pull Request Test Coverage Report for Build 9573392484

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 97.766%

---

Totals
Change from base Build 9520296180:	0.0%
Covered Lines:	36286
Relevant Lines:	37115

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 9573398281

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 97.766%

---

Totals
Change from base Build 9520296180:	0.0%
Covered Lines:	36286
Relevant Lines:	37115

---

💛 - Coveralls

[charliedmcb]

pproved, but does this mean we should lock down who can actually create tags to be scoped directly to our team? Is it already fairly locked down?

We already have restrictions around version tags, but I will do a sanity check over current permissions. Good callout.