More flexible binary and run rules.

[jsirois]

Kill coordinator_of_binaries and implement binary and run validation
separately.

The binary goal now supports both globbing that includes targets that do not
produce a binary as well as production of multiple binaries per target.

The run goal now also supports globbing as long as exactly one of the globbed
targets can produce a binary.

[ci skip-rust-tests]
[ci skip-jvm-tests]

[jsirois]

I was working on an experiment that used two binary targets in the same directory and I went to build them with ./v2 binary src/python/pants/backend/python/rules/pex_tools: and got a blow-up since the directory also contained a common library the binaries used. It was frustrating to not be able to say "build all my binaries" in a ~sane way like I could in v1.

With this change the ergonomics of binary and run change - I think for the better:

Before:

$ ./v2 --no-print-exception-stacktrace binary src/python/pants::
...
ERROR: The `run` and `binary` goals only work with the following target types: ['python_binary']

You used src/python/pants/backend/native/subsystems:subsystems with target type 'python_library'.

After:

$ ./v2 --no-print-exception-stacktrace binary src/python/pants::

Wrote dist/builder-bin.pex
Wrote dist/pants.pex
Wrote dist/pants_local_binary.pex
Wrote dist/resolver-bin.pex
Wrote dist/reversion.pex
Wrote dist/s3_log_aggregator.pex

Before:

$ ./v2 --no-print-exception-stacktrace binary src/python/pants/base:
...
ERROR: The `run` and `binary` goals only work with the following target types: ['python_binary']

You used src/python/pants/base:build_root with target type 'python_library'.

After:

$ ./v2 --no-print-exception-stacktrace binary src/python/pants/base:
...
ERROR: The `binary` goal only works with the following target types:
  * python_binary

You specified `src/python/pants/base:` which only included the following target types:
  * python_library
  * python_tests

The run goal now also supports globbing as long as exactly one of the
globbed targets can produce a binary.

Before:

$ ./v2 --no-print-exception-stacktrace run src/python/pants/util:
...
ERROR: Expected a single target, but was given multiple targets.

Did you mean one of:
  * src/python/pants/util:argutil
  ...
  * src/python/pants/util:xml_parser

After:

$ ./v2 --no-print-exception-stacktrace run src/python/pants/util:


Paths by count:
===============

Paths by bytes:
===============

IPs by count:
=============

IPs by bytes:
=============


Running target: src/python/pants/util:s3_log_aggregator
src/python/pants/util:s3_log_aggregator ran successfully.

Before:

$ ./v2 --no-print-exception-stacktrace run src/python/pants/bin:
...
ERROR: Expected a single target, but was given multiple targets.

Did you mean one of:
  * src/python/pants/bin:bin
  * src/python/pants/bin:pants
  * src/python/pants/bin:pants_local_binary

After:

$ ./v2 --no-print-exception-stacktrace run src/python/pants/bin:
...
ERROR: The `run` goal only works on one binary target but was given multiple targets that can produce a binary:
  * src/python/pants/bin:pants
  * src/python/pants/bin:pants_local_binary

Please select one of these targets to run.

Before:

$ ./v2 --no-print-exception-stacktrace run src/python/pants/base:
...
ERROR: Expected a single target, but was given multiple targets.

Did you mean one of:
  * src/python/pants/base:build_environment
  ...
  * src/python/pants/base:workunit

After:

$ ./v2 --no-print-exception-stacktrace run src/python/pants/base:
...
ERROR: The `run` goal only works with the following target types:
  * python_binary

You specified `src/python/pants/base:` which only included the following target types:
  * python_library
  * python_tests

[jsirois]

Note to self: update with #9528 for improved run_test.

[Eric-Arellano]

Thanks. This is a nice UX win.

[Eric-Arellano]

Huh, neat. Sounds good to me to support globbing.

In a followup, we will likely want to add this flexibility to test --debug:

pants/src/python/pants/rules/core/test.py

Lines 255 to 256 in 45bf1da

	if options.values.debug:
	target_with_origin = targets_with_origins.expect_single()

And we should consider removing the expect_single() methods entirely.

[Eric-Arellano]

This looks great.

Thank you for only factoring one level higher and not more than that - I'm not yet sure how we'll want to generalize all this Config code and want to finish porting lint, repl, and setup-py first.

[Eric-Arellano]

I love how this rule reads now. Wonderful.