fix: Update for pgmonitor-extension 2.1. disable all default collectors in postgres_exporter

[keithf4]

Description

Update pgMontior for changes in pgmonitor-extension 2.1.0. New metrics for sql_exporter and update alerts.

The options currently used in the example sysconfig files for postgres_exporter to disable the default metrics to not disable the new collectors that have been getting added. This hadn't been a problem until PG17 when the builtin bgwriter query broke. We do not use any of the built in metrics, so disable all the collectors in our example. Note this is not an issue in sql_exporter since it has no default DB metrics.

Found that some metrics for pgbouncer_fdw had been misnamed in the sql_exporter collector file. Renamed them to match what they were in postgres_exporer and to also match what the Grafana dashboard is expecting

Fixed an errant double-quote in the sql_exporter pgbouncer fdw metrics file

Please indicate what kind of change your PR includes (multiple selections are acceptable):

• Bugfix
• Enhancement
• Breaking Change
• Documentation

PRs should be against existing issues, so please list each issue using a separate 'closes' line:

closes #456 #398

If this PR depends on another PR or resolution of another issue, please indicate that here using a separate 'depends' line for each dependency.

depends on #

If you have an external dependency (packages, portal updates, etc), add the 'BLOCKED' tag to your PR.

Testing

None of the testing listed below is optional.

• Installation method:
  • Binary install from source, version:
  • OS package repository, distro, and version:
  • Local package server, version:
  • Custom-built package, version:
  • Other:
• PostgreSQL, Specify version(s):
• docs tested with hugo version(s):

Code testing

Have you tested your changes against:

• RedHat/CentOS
• Ubuntu
• Not applicable

If your code touches sql_exporter, have you:

• Tested against all versions of PostgreSQL affected
• Ensure that exporter runs with no scrape errors
• Not applicable

If your code touches node_exporter, have you:

• Ensure that exporter runs with no scrape errors
• Not applicable

If your code touches Prometheus, have you:

• Ensured all configuration changes pass promtool check config
• Ensured all alert rule changes pass promtool check rules
• Prometheus runs without issue
• Alertmanager runs without issue
• Not applicable

If your code touches Grafana, have you:

• Ensured Grafana runs without issue
• Ensured relevant dashboards load without issue
• Not applicable

Checklist:

• I have made corresponding changes to:
  • the documentation
  • the release notes
  • the upgrade doc