fix: Cleanup tags when component is removed

[jithumkunjuraman]

When we receive a deletion request for the resource, we will also try to clean the TagBindings associated, which helps clean up unused tagValues/tagkeys residing on the GCP project

Tested locally the following scenarios:

Multiple Resources created with multiple tags and deleting the resources only deletes the unused tags leaving behind the used tags(Since it is binding to other resources)

Tested change in tag key-values which creates the new ones and deletes the old ones if unused.

Creation and deletion of tags for single resources.

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
Report missing for ba2b2ca1	✅ 0.00%

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (ba2b2ca)	Report Missing	Report Missing	Report Missing
Head commit (d7cb09f)	577	108	18.72%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#28)	68	0	0.00%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}

Footnotes

1. Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct. ↩

[mKeRix]

Left some comments, but the overall logic looks good to me!

[mKeRix]

LGTM, nice work! 🚀

[github-actions]

🎉 This PR is included in version 1.1.3 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀