build: remove curl script and add github secret for NETLIFY_AUTH_TOKEN

[hippee-lee]

Signed-off-by: Matt Hippely mhippely@vmware.com

PR Checklist

Please check if your PR fulfills the following requirements:

• [ ] Tests for the changes have been added (for bug fixes / features)
• [ ] Docs have been added / updated (for bug fixes / features)
• [ ] If applicable, have a visual design approval

PR Type

What kind of change does this PR introduce? Removes the curl script that was downloading the NETLIFY_AUTH_TOKEN from the firebase cloud function. It implements a github secret that sets up the environment more securely.

• [ ] Bugfix
• [ ] Feature
• [ ] Code style update (formatting, local variables)
• [ ] Refactoring (no functional changes, no api changes)
• [x] Build related changes
• [ ] CI related changes
• [ ] Documentation content changes
• [ ] clarity.design website / infrastructure changes
• [ ] Other... Please describe:

What is the current behavior?

Currently build jobs download the NETLIFY_AUTH_TOKEN for commits and PR's from a firebase cloud function for a small set if github container IP's. While this works and is more secure than commiting the AUTH token to code, its not great either.

Issue Number: N/A

What is the new behavior?

This change adds and configures usage of a github secret to initialize the build environment with a github secret for the NETLIFY_AUTH_TOKEN.

Does this PR introduce a breaking change?

• [ ] Yes
• [x] No

Other information