feat: create frontend GitHub actions workflows, added new frontend template

[rak3rman]

Refactored existing Github Actions workflows to make the purpose of each workflow more clear. Added additional workflows and utils to support stand up and teardown of staging envs for the next frontend. Completely wiped the existing frontend in favor of a next.js template that works nicely with Cloudflare Pages. Closes #96.

[github-actions]

Pull Request Smart Comments
Assignee(s): Mark tasks as they are completed. Code Reviewer(s): Ensure all tasks are complete and follow best standards before approving.

• Assigned at least one (1+) experienced code reviewer and notified them requesting a review
• Assigned all contributors as assignees
• Assigned relevant labels that are a subset or related to the parent issue's labels
• Checked that PR description contains a quick summary of work accomplished and uses issue closing words
• Checked that completed tasks in related issue(s) are marked accordingly
• Checked that PR title is descriptive and follows commit message semantics

[rak3rman]

Evidence of the Staging Teardown script working on Github Actions runners: https://github.com/radicalplatforms/shafa/actions/runs/8463035681
Didn't end up testing the Production Deploy script since, well, it deploys to production. I feel confident in the code as it is similar to the Next Integration script.

[vincentdo1]

Workflows look good to me. Question on if we want to initialize a templated frontend structure or have that in an upcoming PR.

[vincentdo1]

L G T M