Renaming directory fails "amplify push"

**Describe the bug**
Renaming directory where an amplify project reside results in failed "amplify push" with reason as below:

> UPDATE_FAILED apinotestaker AWS::CloudFormation::Stack Thu Oct 08 2020 20:18:52 GMT+0800 (China Standard Time) Parameters: [S3DeploymentRootKey, S3DeploymentBucket] must have values

**Amplify CLI Version**
4.16.1

**To Reproduce**
1. create an amplify project which can be pushed successfully.
2. rename name of the project folder.
3. my project components are as:
> | Category | Resource name | Operation | Provider plugin |
| -------- | ------------------------- | --------- | ----------------- |
| Api | notestaker | Update | awscloudformation |
| Auth | notestaker | No Change | awscloudformation |
4. try "amplify push" again.
5. see the error ...
UPDATE_FAILED apinotestaker AWS::CloudFormation::Stack Thu Oct 08 2020 20:18:52 GMT+0800 (China Standard Time) Parameters: [S3DeploymentRootKey, S3DeploymentBucket] must have values

**Expected behavior**
Whether a project can be pushed successfully should have nothing to do with the folder name. At least this should be stated in documents.

**Screenshots**
N/A

**Desktop (please complete the following information):**
- OS: MacOS 10.15.6 (19G73)
- Node Version. 14.0.0

**Additional context**
N/A

No source file or test is named. Start by reproducing the failure with Amplify CLI 4.16.1 after renaming the project directory, then trace how the CLI supplies S3DeploymentRootKey and S3DeploymentBucket to the CloudFormation stack. Done means a renamed project can complete amplify push, or the limitation is clearly documented.

Written by the indexing model from the issue text.