Aws docs n8

[vtnate]

Addresses #167

Pull Request Description

• Make docs a little clearer
• Add link to bsb github repo
• Make AWS CLI version 2 the obviously correct choice. Eliminate outdated advice about venvs, not necessary with version 2
• Remove PII from example yml file
• Include note that dashes are not allowed in project_identifier for AWS

Checklist

Not all may apply

• Code changes (must work)
• Tests exercising your feature/bug fix (check coverage report on CircleCI build -> Artifacts)
• All other unit tests passing
• Update validation for project config yaml file changes
• Update existing documentation
• Run a small batch run to make sure it all works (local is fine, unless an Eagle specific feature)
• Add to the changelog_dev.rst file and propose migration text in the pull request

[vtnate]

@nmerket This should make things a little easier for AWS users.

Did I update the changelog file the way you want? :)

[nmerket]

Thanks for doing this!

[nmerket]

I'm on the fence about whether we need to document in the changelog minor things like this. What do you think, @rHorsey?

[vtnate]

Seems like this is not worthy of changelog, as nothing in the code is actually changing.

[rHorsey]

@vtnate @nmerket As written def not impactful, but I actually think tracking docs changes is critical, not least of all because we seriously need to start 'ataboy-ing' every docs improvement. Also if I go read something and I'm like - since when has this been the recommended way of doing whatever - I can still go find the change to the docs and then hopefully reverse-engineer what's up. I'd just slightly change this to read Made minor clarity updates in configuring local docker and aws setups.

[rHorsey]

Also I really like the idea of every PR that get's merged having an entry - it's something that I see in projects like dask and sqlalchemy and I really like what it does to the culture of development and use of the projects.

[vtnate]

Dunno if it's appropriate here, but in urbanopt we're following the openstudio-extension changelog pattern, and using that script to access the github issues for direct copy/paste into the changelog. It's pretty slick, in my experience, at letting you run the script just before a release and updating the changelog easily. Here is an example changelog built using that script.