Add aws_deploy npm action to build workflow

[vanreece]

Added the scripts/aws_deploy.py script which will run at the end of
github builds and push stuff up to s3, so that you can easily get builds
to reviewers or anyone else without issue.

Needs to have some secrets set up on github to work, documentation is at
the top of the python script.

Of note, currently the --quiet flag is passed to the aws commands, resulting in a less spammy view in the actions log, but, there's three options I considered, and I'm laying them out below:

Full spam (not recommended, showing partial upload info) is here: https://github.com/vanreece/RapiD/runs/2741023491?check_suite_focus=true

--no-progress still shows each file uploaded, but not partial progress: https://github.com/vanreece/RapiD/runs/2766195986?check_suite_focus=true

--quiet doesn't talk at all about individually uploaded files, minimum log spam (current setting): https://github.com/vanreece/RapiD/runs/2766275985?check_suite_focus=true

What do y'all think about those three options?

[Bonkles]

@vanreece I think I like the second log option, just purely from a forensics style 'crime scene' investigation. Good to have a manifest of what the job uploaded, as that would be useful to contrast vs. what's in a given directory at any point in time.

[vanreece]

Yeah, I'm with ya on that one. Will do.

[Bonkles]

This branch CAN actually be merged as it appears to work fine under other circumstances- the reason these builds are failing now is because by security policy, github secrets can't be accessed from PRs that originate from other forks!