We want to make sure that every time we make an update to Compass, when we apply it as an update to latest Compass release in corresponding channel (e.g., we made a change in main branch that corresponds to the dev release channel, when we apply it on top of previous Compass build generated in main branch) it doesn't prompt user for the keychain access.

For that we want to add an e2e test that first finds the latest release for the channel (dev, beta, or ga), runs the app and stores a connection in favorites. After that we "update" the app with the build made from the latest source and check that the app works and doesn't prompt for the keychain password.