terraform-provider-snowflake feat: add snowflake_grant_application

Adds a new resource for grant_application_role. Also adds some stuff to SDK to make it work. Relies on an app package to exist, which may not exist in the current account. No application resource currently exists to use.

Test Plan

[x] acceptance tests

[ ] …

References

https://docs.snowflake.com/en/sql-reference/sql/grant-application-role

Apr 10 '24 00:04 sfc-gh-swinkler

Integration tests failure for e778c23b596b62218059350b8ad0a0316703990d

Apr 10 '24 01:04 github-actions[bot]

Integration tests failure for b5d4406699857e1f6ad94570c1ccdf5a086ef1ef

Apr 12 '24 00:04 github-actions[bot]

Integration tests failure for 1b44738ff10350badc5420afd2fca2dad7a059be

Apr 13 '24 01:04 github-actions[bot]

Integration tests failure for f3f9cb6619921bc7e71fa12d318da1169a2a6347

Apr 13 '24 01:04 github-actions[bot]

Integration tests failure for 06e559994d5a7155916bf48c61180218e31666a0

Apr 13 '24 01:04 github-actions[bot]

Integration tests failure for 40fb6437dad55ad95ad1beff4441b0639990b334

Apr 17 '24 00:04 github-actions[bot]

Integration tests failure for ebcce67df826ca9a0030e049d8078822b5834f9f

Apr 18 '24 04:04 github-actions[bot]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
9467623	Triggered	Generic Password	76365d5ed8d5f45ef6ed25db54b7e87b51f43ee7	pkg/resources/password_policy_acceptance_test.go	View secret
9467623	Triggered	Generic Password	76365d5ed8d5f45ef6ed25db54b7e87b51f43ee7	pkg/resources/password_policy_acceptance_test.go	View secret

🛠 Guidelines to remediate hardcoded secrets

Understand the implications of revoking this secret by investigating where it is used in your code.
Replace and store your secrets safely. Learn here the best practices.
Revoke and rotate these secrets.
If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

following these best practices for managing and storing secrets including API keys and other credentials
install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}