fix: add sync state and context to check previous run details

[mndeveci]

Which issue(s) does this change fix?

N/A

Why is this change necessary?

If customer runs sam sync with a following sam sync --no-dependency-layer for a Java function without making a code change, the second run will fail since cached build will kick in and use the package which doesn't have dependencies in it (since previous run was using ADL which omits the dependencies). This issue only happens for Java runtimes, since we exclude dependencies after build is completed.

How does it address the issue?

By introducing "Sync State" which will keep track of used options in previous session so that sam sync can check if there were any changes and run cleaning operation before starting the sync.

What side effects does this change have?

If customer runs sam sync (with ADL) and then switches to sam sync --no-dependency-layer (without ADL), their cached/incremental builds will be cleaned up so a full build needs to be completed. Sub-sequent runs after this will have cached/incremental builds.

Mandatory Checklist

PRs will only be reviewed after checklist is complete

• Add input/output type hints to new functions/methods
• Write design document if needed (Do I need to write a design document?)
• Write/update unit tests
• Write/update integration tests
• Write/update functional tests if needed
• make pr passes
• make update-reproducible-reqs if dependencies were changed
• Write documentation

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[qingchm]

To capture a few discussion points mentioned in the code review session:

1. The wrapping of the withs for context creation in sync seems to have too many layers, it would be nice to have it refactored to be cleaner. However the shared temp dirs and template file location between contexts, as well as the scheduled delays needs to be preserved, so we need to be careful about it. It would be nice to have a separate PR to address it, but for current release scope we will play safe and leave it as it is right now.
2. As the current behaviour of the sync state stores the dependency layer's status, we explored the possibility of auto-saving this into samconfig.toml. That would help in the scenario where the user deployed the initial application with no-dependency-layer but forget to add this flag in later executions, current solutions will not fill in the previous option value, but instead safely switch to ADL under this scenario. A suggested solution is that after each execution we prompt the user if they want to store the setting into toml. But after discussion with UX, this improvement will be addressed by environment and is not in this PR's scope.
3. Locks will protect one process's thread safety, since for each process only one sync state instance will be instantiated, we will not need of locking mechanism on toml write even though it's not atomic. As for write errors, we will not be catching it since this is consistent with how we do it for build.toml, currently we don't see any issues/dangers.