Excluding non-atomized targets in CI when atomized target exists

[minijus]

Illustrating this feature request/issue by example:

1. There is a repo with projects that have target test.
2. With possibility to atomize, some of the projects are configured to be atomized under test-atomized target.
3. Running CI with multiple targets:

nx affected --targets=test,test-atomized,lint,build

This scenario is troublesome, because:

1. nx affected will create tasks for for test and test-atomized targets. When on CI atomized target would be preferred (there is no way today to configure that atomized target is preferred).
2. Excluding by tag would not work since it would exclude all tasks for project.
3. The only way forward today, is to rename non-atomized target to something else (e.g. test-local). But this is not great DX, developers have to be aware that some projects can be run with test and others with test-local.

Proposal for this feature request is to introduce a way to configure preference of exclusion (or priority) when multiple targets for the same executor are passed into affected/run-many.

If atomized targets could be configurable via configuration, it could look just like this:

nx affected --targets=test,lint,build --configuration=ci

If atomized targets are still defined by separate targets (e.g. test-atomized):

nx affected --targets=test,test-atomized,lint,build --prefer-targets=test-atomized