Remove pg_stat_activity from vacuum monitoring

What does this MR do and why?

Follow-up to !116271 (merged)

It turns out that the user that executes the database migrations can't access pg_stat_activity. But we do have postgres_pg_stat_activity_autovacuum() function than can be used.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

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.