[Bug] auvacuum worker worked in loop and it is caused to High CPU usage

### Apache Cloudberry version

We are trying to test Apache Cloudberry 2.1.0 on Astra Linux 1.8.1 (Debian 12 based)

### What happened

Hello,
We found the next problem with auvacuum worker using not correct logic and trying to vacuum PXF foreghn tables located on Hadoop.
It is caused to high CPU usage by autovacuum workers on database with high coung of PXF tables

In Cloudberry master log we can see many messages by the next screenshoot we can see

When we can run vacuum on problem database, vacuum crashed by the next error

And we can identify this object as PXF foreighn table

### What you think should happen instead

And i think correct about vacuum logic can not work with foreighn tables and in Greenplum logic means not use PXF tables too in this mechanizm.

### How to reproduce

I think need to create couple of PXF tables on clean DB.

### Operating System

Astra Linux 1.8.1 (Debian 12 based)

### Anything else

Every time.

### Are you willing to submit PR?

- [ ] Yes, I am willing to submit a PR!

### Code of Conduct

- [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/cloudberry/blob/main/CODE_OF_CONDUCT.md).

Start by reproducing the loop on a clean database with a couple of PXF foreign tables, then inspect the auvacuum worker logs and the vacuum failure shown in the report. Done means vacuum no longer processes these foreign tables, the worker stops looping, and high CPU usage is eliminated.

Written by the indexing model from the issue text.