Add BATS test for deployment profiles [5d]

[jandubois]

Acceptance Criteria:

Note: Tests will be done via BATS

• Use case 1: system profile and existing settings.json. Expected Output: override only locked properties from system profile, and preserve the remaining properties from settings.json
• Use case 2: system profile and user profile existing settings.json. Expected Output: If there is a system profile, user profile is just ignored. Overrides only locked properties from system profile, and preserve the remaining properties from settings.json
• Use case 3: No profiles and no settings. Json (fresh install). Expected Output: pops-up first-run dialog requesting settings and populate them in settings.json
• Use case 4: System profile, user profile and no settings.json. Expected Output: settings.json will be populated with settings from system profile. User profile will just be ignored.
• Use case 5: Only user profile and no settings. Expected Output: settings.json will be populated with settings from user profile.
• Use case 6: user profile and settings.json. Expected Output: override only locked properties from user profile, and preserve the remaining properties from settings.json
• Use case 7: corrupted system/user profile. Expected Output: System will pop-up an error dialog explicating the profiles have invalid format and will prevent the application to start.
• Use case 8: system profile with incorrect locked property and conflicting settings.json.
• Use case 9: Start Rancher Desktop w/ deployment profiles with non-existing settings
• Use case 10: Start Rancher Desktop with deployment profiles containing wrong data types

[jandubois]

The acceptance criteria from this issue have been copied into epic #4962.