[QA] refactor tests to use real config files

[modSpike]

Pre-submission Checks

• I checked for similar issues, but could not find any. I also checked the closed issues. I could not contribute additional information to any existing issue.
• I will take the time to fill in all the required fields. I know that the bug report may be dismissed otherwise due to lack of information.

Describe the QA issue

as discussed today regarding test failure for PR #12081 using a "fake" or otherwise incomplete config file to bootstrap tests is not ideal so we would like to brainstorm a new approach.

Steps to reproduce the issue

test failure on #12081 is directly related to the missing journalPath setting for the folder in the "fake"/bootstrapping config file. A config generated by the app always includes a value for this setting (as well as all the others)

Important note: I have added a safety check back into the code to handle this situation so the test should now pass (fingers crossed), but we need to remove that as soon as possible because this safety check should never be hit with a normal, complete config file.

Screenshots

Expected behavior

No response

Actual behavior

No response

[modSpike]

important dev note: when this issue is complete, search code for refs to this issue id and fix the code!

[saw-jan]

The agreed solution is to use the full account setup step in all the test scenarios:

client/test/gui/tst_addAccount/test.feature

Lines 23 to 27 in 3d1a2d5

	Given the user has started the client
	When the user adds the following account:
	| server | %local_server% |
	| user | Alice |
	| password | 1234 |

and remove the use of these steps and related codes or refactor them to use the account setup dialog instead of generated config file:

client/test/gui/tst_activity/test.feature

Lines 11 to 13 in 3d1a2d5

	And the user has set up the following accounts with default settings:
	| Alice |
	| Brian |

client/test/gui/tst_activity/test.feature

Line 25 in 3d1a2d5

And user "Alice" has set up a client with default settings

[modSpike]

From our side, Erik had the thought that you could do a snapshot of the env to match the config after running the account setup gui(s). I also think that is a good approach - you could do the snapshot after first test (setting up account and syncs) succeeds then use that snapshot to set up the "clean" state (when required) for each subsequent test in the series.

If it's easier to run the account wizard every time, obviously we have no objections but please do build in tests that reuse a previously created env+config in at least some cases (basically to mimic real user behavior -> set up, do stuff, shut down and run again. Is everything as expected after restart in this scenario?)

[saw-jan]

(basically to mimic real user behavior -> set up, do stuff, shut down and run again. Is everything as expected after restart in this scenario?)

we do have dedicated test scenarios to check that the login is preserved after restarting the client.

client/test/gui/tst_loginLogout/test.feature

Lines 16 to 23 in 3d1a2d5

	Scenario: login after logging out
	Given user "Alice" has set up a client with default settings
	And user "Alice" has logged out from the client-UI
	When user "Alice" logs in using the client-UI
	Then user "Alice" should be connected to the server
	When the user quits the client
	And the user starts the client
	Then user "Alice" should be connected to the server

[saw-jan]

@modSpike we have removed the use of config file in the tests