bskyweb additions

[Jacob2161]

1. Added Mailmodo waitlist API endpoint: POST /waitlist with email parameter. Should anything change here @pfrazee?
2. Added --http-server=:1234 for setting HTTP listen address.
3. Added binary embedded templates/* and static/*
4. Added Dockerfile
5. GitHub Actions for GitHub and AWS (will need to change auth for this again)

[bnewbold]

I think we'll want to automate the hash/commit-in-JS-filename, but can do that in a follow-up PR. I like the templates baked-in, not sure we'll want the (large!) JS bundle in there also, but fine for now.

LGTM!

[bnewbold]

Need to figure out the CI issue though, and CI should also be running after merging to main (looks like that isn't happening right now?).

I think you may just need to add some entries to .prettierignore

[pfrazee]

Sorry I've been slow to respond, just getting out of the swamp.

@Jacob2161 Mailmodo looks right to me. All looking good -- my one question is about the deploy trigger. Right now "main" isn't a safe trigger, so we either need to introduce a dev branch for active work, introduce a "deploy" branch for triggering pushes, or use some other kind of trigger (tags?). Open to ideas here; just need a strong and clear control over the deploy trigger.

@bnewbold I haven't double checked but I'm pretty sure that the expo js-build script is giving the js files unique names per build, which is why I had the post-build script which wrote the scripts template with the latest buildfile names. It's probably correct to remove the scripts template from the repo because it'll change on every build? But if that's the goal we probably need to gitignore it, but make sure it's still being used (at a glance I'm not sure if this PR preserved that).