Doc: update the name for the latest file changes

During our PR review, some new files have changed resulting in the tests
in local comupter failures. So update the old names in these new files
to catch up the latest updates.

src/test/regress/expected/aqumv.out

@@ -2722,7 +2722,7 @@ CREATE READABLE EXTERNAL TABLE aqumv_ext_r(id int)
 FORMAT 'text';
 create materialized view aqumv_ext_mv as
   select * from aqumv_ext_r;
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'id' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'id' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 analyze aqumv_ext_mv;
 explain (costs off, verbose)
@@ -2861,7 +2861,7 @@ analyze t;
 create materialized view mv as
   select sum(c1) as mc1, count(c2) as mc2, avg(c3) as mc3, count(*) as mc4
   from t where c1 > 90 order by 1, sum(c1 - 1) ASC;
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'mc1' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'mc1' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 analyze mv;
 set local enable_answer_query_using_materialized_views = off;
@@ -3022,7 +3022,7 @@ analyze t;
 create materialized view mv as
   select sum(c1) as mc1, count(c2) as mc2, avg(c3) as mc3, count(*) as mc4
   from t where c1 > 90;
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'mc1' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'mc1' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 analyze mv;
 set local enable_answer_query_using_materialized_views = off;

src/test/regress/expected/bfv_joins.out

@@ -11,7 +11,7 @@ create table y (a int, b int, c int);
 NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 insert into y (select * from x);
-CREATE TABLE t1 (a int, b int);
+CREATE TABLE t1 (a int, b int, c int not null);
 NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 CREATE TABLE t2 (a int, b int);

src/test/regress/expected/dynamic_table.out

@@ -108,7 +108,7 @@ ANALYZE dt1;
 -- Create Dynamic Table without DISTRIBUTION KEYS. 
 CREATE DYNAMIC TABLE dt2  AS
   SELECT * FROM t1 WHERE a = 2 WITH NO DATA;
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'b' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'b' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 -- Refresh Dynamic Table WITH NO DATA
 REFRESH DYNAMIC TABLE dt0 WITH NO DATA;
@@ -189,22 +189,22 @@ SELECT schedule, command FROM pg_task WHERE jobname LIKE 'gp_dynamic_table_refre
 CREATE TABLE t2(a int, b int, c int) DISTRIBUTED BY (b);
 CREATE MATERIALIZED VIEW mv_t2 AS
   SELECT * FROM t2 WHERE a > 1;
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'b' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'b' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 -- construct dynamic table from materialized view
 CREATE DYNAMIC TABLE dt3  AS
   SELECT * FROM mv_t2 WHERE a = 2;
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'b' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'b' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 -- construct dynamic table from dynamic table
 CREATE DYNAMIC TABLE dt4  AS
   SELECT * FROM dt3 WHERE b = 3;
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'b' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'b' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 -- construct dynamic table from joins
 CREATE DYNAMIC TABLE dt5  AS
   SELECT * FROM dt3 natural join t2 natural join mv_t2;
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'b' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'b' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 -- construct dynamic table from external table 
 begin;
@@ -248,7 +248,7 @@ SELECT sum(id) FROM ext_r where id > 5;
 
 CREATE DYNAMIC TABLE dt_external  AS
   SELECT * FROM ext_r where id > 5;
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'id' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'id' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 ANALYZE dt_external;
 SHOW optimizer;
@@ -297,7 +297,7 @@ ERROR:  can not drop a internal task "gp_dynamic_table_refresh_17387" paried wit
 DETAIL:  please drop the dynamic table instead
 \unset dtoid
 CREATE DYNAMIC TABLE dt_schedule SCHEDULE '1 2 3 4 5' AS SELECT * FROM t2;
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'b' as the Cloudberry Database data distribution key for this table.
+NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'b' as the Apache Cloudberry data distribution key for this table.
 HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
 SELECT pg_catalog.pg_get_dynamic_table_schedule('dt_schedule'::regclass::oid);
  pg_get_dynamic_table_schedule