(gen2-migration) `lock` command shows unexpected diff on an app with no categories

### How did you install the Amplify CLI?

npm install --no-save @aws-amplify/cli-internal-gen2-migration-experimental-alpha

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

_No response_

### Amplify CLI Version

0.6.0

### What operating system are you using?

Mac

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

No

### Describe the bug

After running `lock` on a brand new project with no categories only amplify init and push we see the`UpdateReplacePolicy` changes shown here.

We need to find out why / is this expected.

### Expected behavior

No diff should be displayed by the `lock` command if this is an expected state.

### Reproduction steps

1. Run `amplify init`
2. Run `gen2-migration lock`

Observe diff printed from the drift detection validation.

### Project Identifier

_No response_

### Log output

```
# Put your logs below this line

```

### 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.