[AQUMV] Store view query in gp_matview_aux for view matching.

[avamingli]

Move materialized views SQLs for AQUMV from pg_rewrite to gp_matview_aux.
This would allow for quicker access and filtering, bypassing the evaluation of the system's 200 built-in rule entries that are often irrelevant.

before this commits:

set enable_answer_query_using_materialized_views =on; explain(analyze, costs off, verbose) selectcount(a) from t_select;
QUERY PLAN
---------------------------------------------------------------------
Gather Motion 3:1 (slice1; segments: 3) (actual time=0.000..0.000
rows=1 loops=1)
Output: count
-> Seq Scan onpublic.mv_insert_select (actual time=0.000..0.000
rows=1 loops=1)
Output: count
Settings: enable_answer_query_using_materialized_views ='on',
optimizer ='off'
Planning Time: 78.942 ms
(slice0) Executor memory: 114K bytes.
(slice1) Executor memory: 114K bytes avg x 3x(0) workers, 114K
bytes max (seg0).
Memory used: 128000kB
Optimizer: Postgres query optimizer
Execution Time: 1.695 ms
(11 rows)

Planning Time: 78.942 ms

after this commits:

explain(analyze, costs off, verbose) selectcount(a) from t_select;
QUERY PLAN
------------------------------------------------------------------------------------------
Finalize Aggregate (actual time=4.000..4.000 rows=1 loops=1)
Output: count(a)
-> Gather Motion 3:1 (slice1; segments: 3) (actual time=4.000..4.000 rows=3 loops=1)
Output: (PARTIAL count(a))
-> Partial Aggregate (actual time=4.000..4.000 rows=1 loops=1)
Output: PARTIAL count(a)
-> Seq Scan onpublic.t_select (actual time=4.000..4.000 rows=0 loops=1)
Output: a
Settings: enable_answer_query_using_materialized_views ='on', optimizer ='off'
Planning Time: 0.623 ms
(slice0) Executor memory: 114K bytes.
(slice1) Executor memory: 112K bytes avg x 3x(0) workers, 112K bytes max (seg0).
Memory used: 128000kB
Optimizer: Postgres query optimizer
Execution Time: 1.670 ms
(15 rows)

Planning Time: 0.623 ms

Authored-by: Zhang Mingli avamingli@gmail.com

Fixes #ISSUE_Number

What does this PR do?

Type of Change

• Bug fix (non-breaking change)
• New feature (non-breaking change)
• Breaking change (fix or feature with breaking changes)
• Documentation update

Breaking Changes

Test Plan

• Unit tests added/updated
• Integration tests added/updated
• Passed make installcheck
• Passed make -C src/test installcheck-cbdb-parallel

Impact

Performance:

User-facing changes:

Dependencies:

Checklist

• Followed contribution guide
• Added/updated documentation
• Reviewed code for security implications
• Requested review from cloudberry committers

Additional Context

CI Skip Instructions

---