Option to store .chalice/deployed folder in S3

It would be great to have an option to store _.chalice/deployed/_ folder content in S3 instead of locally. This will make teamwork easier without need to add this folder into source control.

Start by locating the code that creates and reads the .chalice/deployed folder, then trace how deployment state is used across commands. Review the existing AWS integration and configuration patterns before deciding how an S3-backed option should be selected. Done means teams can share this state through S3 without committing the local folder, while existing local behavior remains available.

Written by the indexing model from the issue text.