Define custom config.yaml file

[cmonfortep]

Similar to being able to define a custom workspace, I wonder if it would be possible to just define a different config file.

Giving some context:
We wanted to disable retries for some test, but right now we are forced to apply that setting to all tests inside the same workspace since it's a config attribute. Not ideal.
Similar, we wanted to use executionOrder, parameter that needs to be defined in the config. However, it fails when flows listed can't be found (due to not being included when running specific tags, include-tags).
I assume we could create a different workspace for each suite that requires a different config, but that will force us to duplicate shared flows across other workspaces.

Thanks!

[Him-Sharma]

I would also like to see this. maestro cloud cli already supports multiple config files, but the option to specify a config file is not available in github action
https://docs.maestro.dev/api-reference/configuration/workspace-configuration#multiple-configs