Add configuration file parameter to test, cloud and record commands

[Hyla96]

Proposed changes

The idea behind this PR is to allow multiple configurations for the same test suite. This comes really handy when having the same app with multiple flavors/schemas: you can run the same test on apps having the same codebase but different flows.

This changes add a new parameter --config to the following commands:
$ maestro cloud
$ maestro test
$ maestro record

The parameter is a path for the configuration file used for the flows.

Examples of use:
$ maestro test --config config/another_config.yml

Testing

• Create a config file with a different name or a directory which is not the root.
• Execute:
• $ maestro test --config your_path_to_the_config/file.yml

[rasyid7]

this is a better approach!
my workaround for this is by using yq

yq e '.includeTags=["Android"]' -i config.yaml
yq e '.excludeTags=["Broken","Flaky"]' -i config.yaml

[bartekpacia]

Hey, thanks a lot! I can see this being quite useful, and it doesn't increase code complexity a lot.

requesting further review from @amanjeetsingh150

[bartekpacia]

The failing test is a false positive caused by #2005

Details

[Hyla96]

@bartekpacia Thanks for addressing the review comments in the pr, I didn't have much time to go through them