Set display_priority on shared configuration template fields (DataDog#23311)

* Set display_priority on shared configuration template fields

* Regenerate conf.yaml.example for mysql and postgres

* Regenerate conf.yaml.example for all integrations; update datadog_checks_dev tests

- Sync 219 conf.yaml.example files (and related auto_conf/conf.yaml.default)
  that were out of sync after adding display_priority to shared templates
- Update datadog_checks_dev unit tests to reflect new display_priority values
  and field ordering in template-generated configs

* Keep tags, service, min_collection_interval at display_priority: 0

* Regenerate conf.yaml.example for mysql and postgres

* Reset all template display_priority to 0

* Revert all non-template file changes

* Fix test_template.py expectations for explicit display_priority: 0 in templates

* Add perf counters

Author: coignetp

datadog_checks_dev/datadog_checks/dev/tooling/templates/configuration/common/perf_counters.yaml

@@ -1,4 +1,5 @@
 - name: metrics
+  display_priority: 0
   fleet_configurable: true
   description: |
     This mapping defines which metrics to collect from the performance

datadog_checks_dev/datadog_checks/dev/tooling/templates/configuration/init_config/db.yaml

@@ -1,4 +1,5 @@
 - name: global_custom_queries
+  display_priority: 0
   fleet_configurable: true
   description: |
     See `custom_queries` defined below.

datadog_checks_dev/datadog_checks/dev/tooling/templates/configuration/init_config/http.yaml

@@ -1,4 +1,5 @@
 - name: proxy
+  display_priority: 0
   fleet_configurable: true
   value:
     example:
@@ -31,6 +32,7 @@
     the client or proxy. If you want to resolve the domains on the proxy
     server, use `socks5h` as the scheme.
 - name: skip_proxy
+  display_priority: 0
   fleet_configurable: true
   value:
     example: false
@@ -39,6 +41,7 @@
     If set to `true`, this makes the check bypass any proxy
     settings enabled and attempt to reach services directly.
 - name: timeout
+  display_priority: 0
   fleet_configurable: true
   value:
     example: 10

datadog_checks_dev/datadog_checks/dev/tooling/templates/configuration/init_config/jmx.yaml

@@ -1,11 +1,13 @@
 - name: is_jmx
+  display_priority: 0
   required: true
   description: Whether or not this file is a configuration for a JMX integration.
   value:
     example: true
     type: boolean
   fleet_configurable: true
 - name: collect_default_metrics
+  display_priority: 0
   description: Whether or not the check should collect all default metrics.
   enabled: true
   value:
@@ -14,6 +16,7 @@
     type: boolean
   fleet_configurable: true
 - name: new_gc_metrics
+  display_priority: 0
   description: |
     Set to true to use better metric names for garbage collection metrics.
     jvm.gc.cms.count   => jvm.gc.minor_collection_count
@@ -28,13 +31,15 @@
     type: boolean
   fleet_configurable: true
 - name: service_check_prefix
+  display_priority: 0
   description: |
     Custom service check prefix. e.g. `my_prefix` to get a service check called `my_prefix.can_connect`.
     If not set, the default service check used is the integration name.
   value:
     type: string
   fleet_configurable: true
 - name: conf
+  display_priority: 0
   description: |
     The list of metrics to be collected by the integration
     Read http://docs.datadoghq.com/integrations/java/ to learn how to customize it

datadog_checks_dev/datadog_checks/dev/tooling/templates/configuration/init_config/perf_counters.yaml

@@ -1,4 +1,5 @@
 - name: use_localized_counters
+  display_priority: 0
   description: |
     Whether performance object and counter names should refer to their
     locale-specific versions rather than their English name.

datadog_checks_dev/datadog_checks/dev/tooling/templates/configuration/init_config/service.yaml

@@ -1,4 +1,5 @@
 name: service
+display_priority: 0
 value:
   type: string
 description: |

datadog_checks_dev/datadog_checks/dev/tooling/templates/configuration/init_config/tags.yaml

@@ -1,4 +1,5 @@
 name: tags
+display_priority: 0
 value:
   example:
     - <KEY_1>:<VALUE_1>

datadog_checks_dev/datadog_checks/dev/tooling/templates/configuration/instances/db.yaml

@@ -1,4 +1,5 @@
 - name: only_custom_queries
+  display_priority: 0
   fleet_configurable: true
   description: |
     Set this parameter to `true` if you want to skip the integration's default metrics collection.
@@ -7,6 +8,7 @@
     type: boolean
     example: false
 - name: use_global_custom_queries
+  display_priority: 0
   fleet_configurable: true
   description: |
     How `global_custom_queries` should be used for this instance. There are 3 options:
@@ -18,6 +20,7 @@
     type: string
     example: "true"
 - name: custom_queries
+  display_priority: 0
   fleet_configurable: true
   description: |
     Each query must have 2 fields, and can have a third optional field:

datadog_checks_dev/datadog_checks/dev/tooling/templates/configuration/instances/default.yaml

@@ -1,5 +1,6 @@
 - template: instances/all_integrations
 - name: disable_generic_tags
+  display_priority: 0
   description: |
     Generic tags such as `cluster` will be replaced by <integration_name>_cluster to avoid
     getting mixed with other integration tags.
@@ -10,6 +11,7 @@
   hidden: true
   fleet_configurable: true
 - name: enable_legacy_tags_normalization
+  display_priority: 0
   description: |
     Whether to enable legacy tags normalization. When enabled (default), hyphens in tag
     values are replaced with underscores. Set to `false` to preserve hyphens, which is
@@ -21,6 +23,7 @@
   hidden: true
   fleet_configurable: true
 - name: metric_patterns
+  display_priority: 0
   description: |
     A mapping of metrics to include or exclude, with each entry being a regular expression.
 

datadog_checks_dev/datadog_checks/dev/tooling/templates/configuration/instances/global.yaml

@@ -1,4 +1,5 @@
 - name: min_collection_interval
+  display_priority: 0
   value:
     example: 15
     type: number
@@ -7,6 +8,7 @@
     https://docs.datadoghq.com/developers/write_agent_check/#collection-interval
   fleet_configurable: true
 - name: empty_default_hostname
+  display_priority: 0
   value:
     example: false
     type: boolean