feat(misc): prepend cwd to directory in project generators when using as-provided format

[leosvelperez]

Current Behavior

When generating a new project using the as-provided project name and root format, the current working directory is ignored.

Expected Behavior

When generating a new project using the as-provided project name and root format, it should consider the current working directory.

# cwd=.
nx g app app1
# directory: app1

# cwd=apps
nx g app app1
# directory: apps/app1

# cwd=apps
nx g app app1 --directory nested/app1
# directory: apps/nested/app1

# cwd=apps/nested
nx g app app1 --directory apps/nested/app1
# directory: apps/nested/app1 (the directory starts with the cwd, it's used as is)

Related Issue(s)

Fixes #

[vercel]

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

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview		Sep 22, 2023 8:34am

[nx-cloud]

☁️ Nx Cloud Report

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

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 6 targets

• nx affected --target=e2e --base=903c4fe7c83bb670cdf047a28506b9be228c991a --head=a8a6852e73153d5db007640beaa3ff41cc00ad92 --parallel=1
• nx affected --targets=lint,test,build --base=903c4fe7c83bb670cdf047a28506b9be228c991a --head=a8a6852e73153d5db007640beaa3ff41cc00ad92 --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=903c4fe7c83bb670cdf047a28506b9be228c991a --head=a8a6852e73153d5db007640beaa3ff41cc00ad92
• nx documentation --no-dte
• nx affected -t e2e-macos --parallel=1 --base=903c4fe7c83bb670cdf047a28506b9be228c991a --head=a8a6852e73153d5db007640beaa3ff41cc00ad92

---

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.