Description of problem:

PostgreSQL process name pattern is wrong in PCP foreman-hotproc config file, leading to a not monitored service.

How reproducible:

Always

Is this issue a regression from an earlier version:

No.

Steps to Reproduce:

1. Configure PCP as per the "Monitoring Satellite performance" guide (https://docs.redhat.com/en/documentation/red_hat_satellite/6.18/html-single/monitoring_satellite_performance/index#configuring-pcp-data-collection_monitoring):

Querying the list of monitored processes will miss PostgreSQL ones:

# pmval hotproc.psinfo.rss | grep -e postmaster -e postgres
# 

Actual behavior:
The current code in https://github.com/theforeman/foreman/blob/develop/extras/pcp/foreman-hotproc.conf#L7 will look only for processes that contain both "postgres" AND "-D".

But the current names are like this:

# ps auxw | grep -w -e postgres -e postmaster
postgres  139026  0.1  0.3 4429260 112736 ?      Ss   Jan08   1:49 /usr/bin/postmaster -D /var/lib/pgsql/data
postgres  139027  0.0  0.0  91644 20752 ?        Ss   Jan08   0:00 postgres: logger 
postgres  139029  0.0  7.7 4430672 2531748 ?     Ss   Jan08   0:36 postgres: checkpointer
. . . 

Expected behavior:
`pmval` and related PCP commands should show the PostgreSQL related processes.

Business Impact / Additional info:

Fix in https://github.com/theforeman/foreman/pull/10815.