Fix no tests being run when flowsOrder specified all tests in the workspace

[bartekpacia]

Attempts to fix #1971

[bartekpacia]

Investigation results

This bug is introduced by #1732. Offending source code:

maestro/maestro-cli/src/main/java/maestro/cli/command/TestCommand.kt

Lines 197 to 198 in a9575c5

	val effectiveShards = shards.coerceAtMost(plan.flowsToRun.size)
	val chunkPlans = plan.flowsToRun

It occurs only when all flows are specified in executionOrder.flowsOrder. Take this config.yaml as an example:

flows:
  - "features/**"
includeTags:
  - regression
executionOrder:
    continueOnFailure: true
    flowsOrder:
        - test1
        - test2
        - test3

If in features/ there is only test1.yaml, test2.yaml, and test3.yaml, then the bug occurs. But if we add test_other.yaml, then the bug is fixed.

Fix: when running in a single shard, add ExecutionPlan.sequence at the beginning of the queue of flows to execute.

Also, I'd like to have a bit more output logging.