Documentation can lead to a vulnerable package to be downloaded #6654
Description
Before opening, please confirm:
- I have searched for duplicate or closed issues and discussions.
- I have read the guide for submitting bug reports.
- I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
JavaScript Framework
Angular
Amplify APIs
Authentication
Amplify Version
v5
Amplify Categories
auth
Backend
Amplify CLI
Environment information
This link to documentation https://ui.docs.amplify.aws/angular/connected-components/authenticator#setup-with-amplify-gen-2-backend references v4 and v4 happens to be a npm project. Inadvertently someone can do this npm install @aws-amplify/ui-angular v4 and v4 happens to be a npm package. Please remove v4 from the documentation as it can lead to a v4 being installed.
```
# Put output below this line
</details>
### Describe the bug
This link to documentation https://ui.docs.amplify.aws/angular/connected-components/authenticator#setup-with-amplify-gen-2-backend references v4 and v4 happens to be a npm project. Inadvertently someone can do this npm install @aws-amplify/ui-angular v4 and v4 happens to be a npm package. Please remove v4 from the documentation as it can lead to a v4 being installed.
### Expected behavior
Remove v4 from documentation
### Reproduction steps
go to https://ui.docs.amplify.aws/angular/connected-components/authenticator#setup-with-amplify-gen-2-backend and v4 should be removed maybe say version 4
### Code Snippet
```javascript
// Put your code below this line.
Log output
// Put your logs below this line
aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response