E2E test: quarantine app settings tests in airgapped job

What does this MR do?

This quarantines tests (for the nightly airgapped job only) where application settings are modified.

We are investigating the cause of these failures in: #414247 (closed) and #421259 (comment 1503796117)

E2E Test Failure issue(s)

The below failures can be seen in the latest nightly Allure report: http://gitlab-qa-allure-reports.s3.amazonaws.com/nightly/master/975318576/index.html#suites/09d0a3f3f0fa3d5a05074518fb18aedd

• 1: #416697 (closed) & #413726 (closed)
• 2: #413728 (closed)
• 3: #416586 (closed)
• 4: #421259

Check-list

• General code guidelines check-list
  • Code review guidelines
  • Style guides
• Quarantine test check-list
  • Follow the Quarantining Tests guide.
  • Confirm the test has a quarantine: tag with the specified quarantine type.
  • Note if the test should be quarantined for a specific environment.
  • (Optionally) In case of an emergency (e.g. blocked deployments), consider adding labels to pick into auto-deploy (Pick into auto-deploy priority1 severity1).
• Dequarantine test check-list
  • Follow the Dequarantining Tests guide.
  • Confirm the test consistently passes on the target GitLab environment(s).
• To ensure a faster turnaround, ask in the #quality_maintainers Slack channel for someone to review and merge the merge request, rather than assigning it directly.