[Maestro cloud] Emulator losing location after using setLocation

[pimentones]

Describe the bug We have a test using the setLocation command which was setting the location successfully on the emulator/simulator when running tests in the maestro cloud but now the tests fail because the location is reset.

To Reproduce

1. Use the setLocation command
2. Run the tests on the cloud

Expected behavior The emulator runs the tests using the location set by setLocation command

Screenshots

Bugreport output (if applicable) The zip files created when maestro bugreport can be uploaded here as well if applicable.

Additional context Link to report in slack

Although in the setLocation command page you say the following:

Note that this does not update the location of the emulator/simulator when running in Maestro Cloud so if your backend/app relies on IP location, this will still be set to the default location which is US

we were able to run tests on the maestro cloud using the setLocation location properly but since around the 28th of October the tests are failing