Promoting alert settings specs to smoke

What does this MR do and why?

Describe in detail what your merge request does and why.

These tests:

• qa/qa/specs/features/browser_ui/8_monitor/alert_management/create_alert_using_authorization_key_spec.rb
• qa/qa/specs/features/browser_ui/8_monitor/alert_management/alert_settings_create_new_alerts_spec.rb

Have been quite stable and they cover essential/basic functionalities in grouprespond . Promoting them to :smoke - I know I skip :reliable state but these have been stable since the day they were merged. Plus grouprespond doesn't have any smoke tests yet, I think it's fair to move them to :smoke bucket.

Test execution metrics

• Monitor Alert settings when using HTTP endpoint integration behaves like sends test alert using authorization key creates new alert - https://gitlab.com/gitlab-org/gitlab/-/quality/test_cases/386734#executions
• Monitor Alert settings when using Prometheus integration behaves like sends test alert using authorization key creates new alert - https://gitlab.com/gitlab-org/gitlab/-/quality/test_cases/386735#executions
• Monitor Alert settings when using HTTP endpoint integration behaves like sends test alert creates new alert - https://gitlab.com/gitlab-org/gitlab/-/quality/test_cases/382803#executions
• Monitor Alert settings when using Prometheus integration behaves like sends test alert creates new alert - https://gitlab.com/gitlab-org/gitlab/-/quality/test_cases/385792#executions

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.