ci: add workflow to build for web

[staceybeard]

By submitting this merge request, I confirm the following:

• The merge request title follows the conventional commits convention (see Backend project's README.md)
  • feat: minor app version will be incremented.
  • fix, deps, perf: patch app version will be incremented.
  • chore, ci, etc.: app version will not be incremented.
  • See semantic-release/commit-analyzer
    for complete set of rules.

Changes

Wrote a workflow to build and deploy the app for web via GitHub Actions. This is done automatically for dev, and can be run manually for other environments.

Dependencies

• Listener: N/A

[mschoettle]

LGTM

In hindsight I think it would have been cleaner to avoid the environment in caps and just named the secret/var name with a lowercase env name.

[staceybeard]

In hindsight I think it would have been cleaner to avoid the environment in caps and just named the secret/var name with a lowercase env name.

True, I'll think about changing that. We could make all the vars lowercase; I haven't seen the uppercase convention used much in GitHub guides.

[staceybeard]

True, I'll think about changing that. We could make all the vars lowercase; I haven't seen the uppercase convention used much in GitHub guides.

Update: the vars are case-insensitive, and actually automatically capitalize themselves when you create them. I'll remove the capitalization of the environment name since it isn't necessary to access the variables.