Automate deployment profile tests via E2E

[IsaSih]

Problem Description

BATS will be used (#4962) to verify whether the default and locked fields are being applied to settings.json. Also, that locked fields are not editable by the user via CLI.

The purpose of this epic is to create e2e tests to verify if the first-run dialog is not shown once there's a deployment profile (wether it's SYSTEM's or USER's). If first-run dialog is shown if there are no profiles and settings.json. Also, if locked fields are locked in the UI + not editable.

Proposed Solution

Develop tests to cover the following scenarios on all 3 platforms:

• NO profiles and NO settings.json (first-run dialog)

• Start Rancher Desktop with SYSTEM deployment profiles, no settings.json

• SYSTEM profile and existing settings.json

• SYSTEM profile and USER profile existing settings.json

• SYSTEM profile and USER profile, no existing settings.json

• Start Rancher Desktop with USER deployment profiles only

• USER deployment profile and existing settings.json

• Start Rancher Desktop w/ deployment profiles with non-existing settings

• Start Rancher Desktop with deployment profiles containing wrong data types

• Start Rancher Desktop w/ bad-formatted deployment profiles

Additional Information

Expected results for each test case is described in the BATS epic #4962.