Upgrade instructions misses a couple of catalog tables

## Why are we implementing it? (sales eng)
There have been some new catalog tables added to citus last year that are not in the upgrade description. Tables that come to mind that are missing
- pg_dist_poolinfo
- pg_dist_authinfo

### What are the typical use cases?
keeping track of citus catalogs during upgrades.

## Communication goals (e.g. detailed howto vs orientation)

### Good locations for content in docs structure
https://docs.citusdata.com/en/v8.2/admin_guide/upgrading_citus.html?highlight=upgrade#on-every-node-coordinator-and-workers

## How does this work? (devs)
pg_catalog is not preserved during upgrades, we have some instructions to keep the tables around, but not all tables are preserved.

### Example sql

### Corner cases, gotchas
Oid's are not preserved for all objects during upgrades, tables having oid's in them might need extra instructions.

### Are there relevant blog posts or outside documentation about the concept/feature?

### Link to relevant commits and regression tests if applicable