Separate Managed Services for Airflow (apache#17926)

The information which service Airflow is installed at is much more
useful than just knowing that it is a Managed Service.

Also added a comment to direct users of Managed Services to the
regular support of those services first.

.github/ISSUE_TEMPLATE/airflow_bug_report.yml

@@ -50,15 +50,19 @@ body:
   - type: dropdown
     attributes:
       label: Deployment
-      description: What kind of deployment do you have?
+      description: >
+        What kind of deployment do you have? If you use Managed Service, consider first using regular
+        channels of reporting issues for the service.
       multiple: false
       options:
-        - "Managed Services (Astronomer, Composer, MWAA etc.)"
         - "Official Apache Airflow Helm Chart"
         - "Other 3rd-party Helm chart"
         - "Docker-Compose"
         - "Other Docker-based deployment"
         - "Virtualenv installation"
+        - "Astronomer"
+        - "Composer"
+        - "MWAA"
         - "Other"
     validations:
       required: true

.github/ISSUE_TEMPLATE/airflow_providers_bug_report.yml

@@ -128,15 +128,19 @@ body:
   - type: dropdown
     attributes:
       label: Deployment
-      description: What kind of deployment do you have?
+      description: >
+        What kind of deployment do you have? If you use Managed Service, consider first using regular
+        channels of reporting issues for the service.
       multiple: false
       options:
-        - "Managed Services (Astronomer, Composer, MWAA etc.)"
         - "Official Apache Airflow Helm Chart"
         - "Other 3rd-party Helm chart"
         - "Docker-Compose"
         - "Other Docker-based deployment"
         - "Virtualenv installation"
+        - "Astronomer"
+        - "Composer"
+        - "MWAA"
         - "Other"
     validations:
       required: true