Parameters: [hostedUIDomainName, autoVerifiedAttributes, ... ] must have values

### How did you install the Amplify CLI?

npm

### If applicable, what version of Node.js are you using?

v16.15.1

### Amplify CLI Version

10.7.1

### What operating system are you using?

windows

### Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

no

### Describe the bug

As soon as I modify any resouorce (i.e some lambda code), when I push I get an error like this:

🛑 The following resources failed to deploy:
Resource Name: auth (AWS::CloudFormation::Stack)
Event Type: update
Reason: Parameters: [hostedUIDomainName, autoVerifiedAttributes, allowUnauthenticatedIdentities, hostedUI, smsVerificationMessage, breakCircularDependency, oAuthMetadata, mfaTypes, userpoolClientGenerateSecret, mfaConfiguration, authProvidersUserPool, adminQueries, permissions, resourceNameTruncated,
userPoolGroups, smsAuthenticationMessage, passwordPolicyMinLength, userPoolName, userpoolClientWriteAttributes, dependsOn, useEnabledMfas, parentStack, resourceName, triggers, unauthRoleArn, requiredAttributes, authTriggerConnections, aliasAttributes, userpoolClientLambdaRole, authRoleArn, userpoolClientReadAttributes, emailVerificationSubject, sharedId, useDefault, identityPoolName, userPoolGroupList, authSelections, hostedUIProviderMeta, usernameCaseSensitive, serviceName, emailVerificationMessage, userpoolClientRefreshTokenValidity, userpoolClientSetAttributes, passwordPolicyCharacters, defaultPasswordPolicy] must have values
URL: https://console.aws.amazon.com/cloudformation/home?region=eu-central-1#/stacks//events
Cli version: 10.7.0

Don't know if this is relevant, but after issueing amplify push I see the section parameters inside file backend-config.json completely wiped out. I mean all entries like AMPLIFY_function__deploymentBucketName or AMPLIFY_function__s3Key and similar.

### Expected behavior

Stack deploys correctly

### Reproduction steps

I modify some lambda code.
When I amplify push, I get many errors, with these reasons:

Reason: Parameters: [authRoleArn, cloudWatchPolicyName, cloudformationPolicyName, unauthRoleName, appName, pinpointPolicyName, unauthPolicyName, authRoleName, roleName, authPolicyName] must have values

Reason: Parameters: [hostedUIDomainName, autoVerifiedAttributes, allowUnauthenticatedIdentities, hostedUI, smsVerificationMessage, breakCircularDependency, oAuthMetadata, mfaTypes, userpoolClientGenerateSecret, mfaConfiguration, authProvidersUserPool, adminQueries, permissions, resourceNameTruncated, userPoolGroups, smsAuthenticationMessage, passwordPolicyMinLength, userPoolName, userpoolClientWriteAttributes, dependsOn, useEnabledMfas, parentStack, resourceName, triggers, unauthRoleArn, requiredAttributes, authTriggerConnections, aliasAttributes, userpoolClientLambdaRole, authRoleArn, userpoolClientReadAttributes, emailVerificationSubject, sharedId, useDefault, identityPoolName, userPoolGroupList, authSelections, hostedUIProviderMeta, usernameCaseSensitive, serviceName, emailVerificationMessage, userpoolClientRefreshTokenValidity, userpoolClientSetAttributes, passwordPolicyCharacters, defaultPasswordPolicy] must have values

Reason: Parameters: [runtimes] must have values

Reason: Parameters: [unauthRoleName, S3DeploymentRootKey, AuthCognitoUserPoolId, authRoleName, S3DeploymentBucket] must have values

### Project Identifier

a635dc80e769ec2b4614a7e43c92b5be

### Log output

_No response_

### Additional information

_No response_

### Before submitting, please confirm:

- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.

Start with amplify push and the parameters section of backend-config.json, then trace how the listed CloudFormation stack parameters are generated during a push. Reproduce on Windows with Amplify CLI 10.7.1 using the supplied Lambda-edit workflow; done means the required parameters remain present and the auth, role, Lambda, and dependent stacks deploy successfully.

Written by the indexing model from the issue text.