fix(angular): fixing application generator when using protractor

[ashley-hunter]

Current Behavior

When generating a new Angular application in an empty workspace (using v2 workspace.json format and standaloneConfig=true) the project fails to generate:

nx generate @nrwl/angular:application --name=sample --e2eTestRunner=protractor --standaloneConfig

This throws the following error:

Cannot find configuration for 'sample-e2e' in /workspace.json.

The issue seems to be that it tries to convert the project to use a standalone config before the e2e project has been created. This seems to be a duplicated step as this happens again in the same generator (after the e2e project has been created):

Expected Behavior

The project should generate successfully.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/nrwl/nx-dev/CecLYbdqckdG6TA7Hc3VkrpQcKUc
✅ Preview: Canceled

[Deployment for f791369 canceled]

[nx-cloud]

Nx Cloud Report

CI ran the following commands for commit f791369. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

Status	Command
	nx affected --target=e2e --base=c08f506c5cd210b3481bf669d899b86631b9dab0 --head=f7913696a465c479e782b7a044b8dd1d3c512337 --exclude=e2e-react-native,e2e-detox
	nx affected --target=lint --base=c08f506c5cd210b3481bf669d899b86631b9dab0 --head=f7913696a465c479e782b7a044b8dd1d3c512337 --parallel --max-parallel=4
	nx affected --target=test --base=c08f506c5cd210b3481bf669d899b86631b9dab0 --head=f7913696a465c479e782b7a044b8dd1d3c512337 --parallel --max-parallel=2
	nx affected --target=build --base=c08f506c5cd210b3481bf669d899b86631b9dab0 --head=f7913696a465c479e782b7a044b8dd1d3c512337 --parallel --max-parallel=3
	nx build typedoc-theme

---

Sent with 💌 from NxCloud.

[AgentEnder]

LGTM 🎉

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.