amplify import auth generates mutiple resources of auth in teams provider info

### Before opening, please confirm:

- [X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-cli/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-cli/blob/dev/CONTRIBUTING.md#bug-reports).
- [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.

### How did you install the Amplify CLI?

_No response_

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

_No response_

### Amplify CLI Version

10.0.0

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

### Amplify Categories

auth

### Amplify Commands

pull

### Describe the bug

Creating a new application then importing a new Cogntio resource then pulling the amplify backend without pushing then re-importing the auth resource will leave redundant auth resource in team-provider-info.json.

### Expected behavior

maintain only one resource oauth to prevent any unexpected issues in teams provider info

### Reproduction steps

1. amplify init
2. amplify import auth
3. amplify pull (do not push)
4. amplify import auth
check another auth resource in team provider info
5. amplify push
aws exports is correct but team provider has multiple blocks

### GraphQL schema(s)

```graphql
# Put schemas below this line

```

### Project Identifier

_No response_

### Log output

```
# Put your logs below this line

```

### Additional information

_No response_