[ENH] Deployment guide updates

[itaismith]

Description of changes

• New dedicated Docker guide.
• Updated AWS guide.
• Dedicated authentication section for both Docker and AWS.
• Update Cloudformation template, with a separate docker-compose file for better maintainability.

Test plan

Followed instructions to verify things are working.

• Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes

This PR

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[atroyn]

Comments in Vercel. Additionally (possibly as follow-ups):

• let's move thin-client out of the main guides
• let's think about how we are going to separate 'client/server' from the main guide
• let point at the deployment documentation at appropriate sections in the docs
• let's add the perf evals in this section

[atroyn]

send it