Inconsistencies in Amplify init framework selection flow

### How did you install the Amplify CLI?

_No response_

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

_No response_

### Amplify CLI Version

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

When running init a empty folder, the following occurs
when selecting `angular` as framework the init fails with and error about a missing file

while the other frameworks allows you to create the env.

while selecting say `ios` as app which requires `xcode` the cli fails at the end not start

### Expected behavior

consistency in flows and document requirements

### Reproduction steps

1. amplify init
2. select angular as framework

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

Start by reproducing `amplify init` in an empty folder with Angular selected on Amplify CLI 12.4.0, then compare its framework-selection flow with the other choices and with iOS. Done means required framework prerequisites are handled consistently and the requirements are documented.

Written by the indexing model from the issue text.