Amplify new console output created duplicates (Amplify v.10.0.0)

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

npm install -g @aws-amplify/cli

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

v14.19.3

### Amplify CLI Version

10.0.0

### What operating system are you using?

Windows 10

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

i didn't made any manual changes on cloud resources.

### Amplify Categories

auth, custom, storage, function, api, hosting

### Amplify Commands

publish, push

### Describe the bug

Hello,

With Amplify Cli V10 there was a new Logging introduced, which should improve the logging experience on amplify push/publish.
It should look like these:

Unfortunately the new logging produces a lot of identical logs in my project.
i use windows 10 and git bash.

With the new logging, there are so many logs written, that i can't scroll up to the beginning after it's finished.
It produces identical logs like these on mass.

For me this is currently a showstopper and I had to downgrade the amplify cli.

Kind Regards
Stefan

### Expected behavior

The Amplify cli shouldn't produced unecassary duplicate logs.

### Reproduction steps

1. Amplify env checkout
2. Amplify push --yes

### GraphQL schema(s)

_No response_

### Project Identifier

_No response_

### Log output

_No response_

### Additional information

_No response_

Reproduce the issue on Windows 10 with Git Bash using `amplify env checkout ` followed by `amplify push --yes`, with Amplify CLI 10.0.0 and Node.js 14.19.3. Trace the CLI logging path responsible for the repeated output and verify that each log is emitted once without preventing the normal push or publish progress from being shown.

Written by the indexing model from the issue text.