…'.odo_cmd_<name>.pid'

The implementation in kubeexec.go is indeed able to run any kind of commands,
not only Devfile-related.

Drop validation rules that prevented from going further
with composite run or debug commands.

…point overridden or env vars updated

The previous implementation was limited to Exec commands solely.
This now makes it easier to support other kind of commands.
For example, when handling a composite command, we are now recursively
determining the containers (a.k.a components) that would get used by this composite command.

This allows to more accurately determine how the process could be reported.

…ent of lines

…site command

This way, users would be able to display them (and follow them) with `odo logs` or `kubectl logs`

…xited

Build commands (which could also be composite ones)
might be executed in a container different from the run or debug ones.

…D 1 process streams

This way, we can also have them displayed with `odo logs` or `kubectl logs`.
This includes Build and Devfile events commands.

…ere not empty

This reduces the clutter in case of an error with the command execution.

…ebug commands running in different containers and with a shared volume)

…elated command is done