fix(misc): refine the prompts in create-nx-workspace

[FrozenPandaz]

Current Behavior

The current prompts for create-nx-workspace do not point out that you can use webpack when creating a standalone react app

The node option is quite lengthy

There's some inconsistent capitalization of ESLint

Expected Behavior

The react option points out that you can still pick webpack

The node option is shortened a bit.

ESLint is consistently capitalized

Related Issue(s)

Fixes #

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
nx-dev	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Jan 23, 2023 at 9:52PM (UTC)

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 9d64da9. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

🟥 Failed Commands
nx documentation --no-dte

✅ Successfully ran 8 targets

• nx run-many -t e2e-macos --parallel=1 --exclude=e2e-detox
• nx affected --target=e2e --base=ef215e99e186c2f48c73105ef6783500340f9d54 --head=9d64da93d08ac7511537d0603a80a35994d2460b --exclude=e2e-storybook,e2e-storybook-angular --parallel=1
• nx affected --target=build --base=ef215e99e186c2f48c73105ef6783500340f9d54 --head=9d64da93d08ac7511537d0603a80a35994d2460b --parallel=3
• nx affected --target=test --base=ef215e99e186c2f48c73105ef6783500340f9d54 --head=9d64da93d08ac7511537d0603a80a35994d2460b --parallel=1
• nx run-many -t root-lint check-imports check-commit check-lock-files depcheck --parallel=1 --no-dte
• nx affected --target=lint --base=ef215e99e186c2f48c73105ef6783500340f9d54 --head=9d64da93d08ac7511537d0603a80a35994d2460b --parallel=3
• nx-cloud record -- nx format:check --base=ef215e99e186c2f48c73105ef6783500340f9d54 --head=9d64da93d08ac7511537d0603a80a35994d2460b
• nx documentation --no-dte

---

Sent with 💌 from NxCloud.

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