fix(core): use defaultConfiguration in run-many and affected when no configuration is specified

[leosvelperez]

Current Behavior

When having a project with say "defaultConfiguration": "production" configured and running nx build project-name, it will apply the default configuration and run nx run project-name:build:production. This is the expected behavior and if we run nx build project-name multiple times without any changes, it will use the cache as expected.

However, if we run nx run-many --target=build --projects=project-name it misses the cache because it runs nx run project-name:build without the default configuration. The same happens when running nx affected:build (being project-name affected), it misses the cache because it doesn't use the configured default configuration.

Expected Behavior

Using run-many or affected:* commands without specifying the configuration should use the defaultConfiguration if provided.

Related Issue(s)

Fixes #

[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/A74PxqJJYMg1Lja3r7mZBHDx5cFP
✅ Preview: Canceled

[nx-cloud]

Nx Cloud Report

CI ran the following commands for commit d01f8a9. 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=1b6c0ee7fab95c352002228c7be73fee25f7a71d
	nx affected --target=lint --base=1b6c0ee7fab95c352002228c7be73fee25f7a71d --parallel --max-parallel=4
	nx affected --target=test --base=1b6c0ee7fab95c352002228c7be73fee25f7a71d --parallel --max-parallel=2
	nx affected --target=build --base=1b6c0ee7fab95c352002228c7be73fee25f7a71d --parallel --max-parallel=3
	nx build typedoc-theme

---

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.