Cleanup: update old brand to Apache Cloudberry

In this PR, delete these lines with old brand `Cloudberry Database` in
some files. This PR is used for cleaning up for better compliance with
ASF rules.

Author: tuhaihe

src/test/regress/expected/aqumv.out

@@ -3173,31 +3173,23 @@ abort;
 create table par(a int, b int, c int) partition by range(b)
     subpartition by range(c) subpartition template (start (1) end (3) every (1))
     (start(1) end(3) every(1));
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Cloudberry Database 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 par values(1, 1, 1), (1, 1, 2), (2, 2, 1), (2, 2, 2);
 insert into par values(1, 1, 1), (1, 1, 2), (2, 2, 1), (2, 2, 2);
 insert into par values(1, 1, 1), (1, 1, 2), (2, 2, 1), (2, 2, 2);
 create materialized view mv_par as select    count(*) from par;
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'count' as the Cloudberry Database 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 materialized view mv_par1 as select   count(*) from par_1_prt_1;
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'count' as the Cloudberry Database 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 materialized view mv_par1_1 as select count(*) from par_1_prt_1_2_prt_1;
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'count' as the Cloudberry Database 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 materialized view mv_par1_2 as select count(*) from par_1_prt_1_2_prt_2;
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'count' as the Cloudberry Database 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 materialized view mv_par2 as select   count(*) from par_1_prt_2;
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'count' as the Cloudberry Database 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 materialized view mv_par2_2 as select count(*) from par_1_prt_2_2_prt_1;
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'count' as the Cloudberry Database 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 materialized view mv_par_prune as select count(*) from par where b = 1;
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'count' as the Cloudberry Database 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.
 set enable_answer_query_using_materialized_views = on;
 explain(costs off, verbose)

src/test/regress/expected/gp_runtime_filter.out

@@ -391,10 +391,8 @@ NOTICE:  table "t1" does not exist, skipping
 DROP TABLE IF EXISTS t2;
 NOTICE:  table "t2" does not exist, skipping
 CREATE TABLE t1(c1 int, c2 int);
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'c1' as the Cloudberry Database 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(c1 int, c2 int);
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'c1' as the Cloudberry Database 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 t1 SELECT GENERATE_SERIES(1, 1000), GENERATE_SERIES(1, 1000);
 INSERT INTO t2 SELECT * FROM t1;
@@ -426,7 +424,6 @@ DROP TABLE IF EXISTS t2;
 NOTICE:  table "t2" does not exist, skipping
 CREATE TABLE t1(c1 int, c2 int, c3 char(50), c4 char(50), c5 char(50)) DISTRIBUTED REPLICATED;
 CREATE TABLE t2(c1 int, c2 int, c3 char(50), c4 char(50), c5 char(50));
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'c1' as the Cloudberry Database 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 t1 VALUES (5,5,5,5,5), (3,3,3,3,3), (4,4,4,4,4);
 INSERT INTO t2 VALUES (1,1,1,1,1), (2,2,2,2,2), (3,3,3,3,3), (4,4,4,4,4);

src/test/regress/expected/gpctas_optimizer.out

@@ -256,7 +256,6 @@ select action::text, b from ctas_baz order by 1,2 limit 5;
 -- Once upon a time, we had a bug in dispatching the table's OID in this
 -- scenario.
 create table ctas_input(x int);
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'x' as the Cloudberry Database 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 ctas_input select * from generate_series(1, 10);
 CREATE FUNCTION ctas_inputArray() RETURNS INT[] AS $$
@@ -270,7 +269,6 @@ $$ LANGUAGE plpgsql;
 create table ctas_output as select ctas_inputArray()::int[] as x;
 INFO:  GPORCA failed to produce a plan, falling back to Postgres-based planner
 DETAIL:  Falling back to Postgres-based planner because GPORCA does not support the following feature: SIRV functions
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'x' as the Cloudberry Database 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.
 INFO:  GPORCA failed to produce a plan, falling back to Postgres-based planner
 DETAIL:  Falling back to Postgres-based planner because GPORCA does not support the following feature: Non-Scalar Subquery
@@ -331,7 +329,6 @@ $BODY$ LANGUAGE SQL IMMUTABLE
 DROP TABLE IF EXISTS unnest_2d_tbl01;
 NOTICE:  table "unnest_2d_tbl01" does not exist, skipping
 CREATE TABLE unnest_2d_tbl01 (id INT, val DOUBLE PRECISION[][]);
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'id' as the Cloudberry Database 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 unnest_2d_tbl01 VALUES
   (1, ARRAY[[1::float8,2],[3::float8,4],[5::float8,6],[7::float8,8]]),
@@ -342,12 +339,10 @@ NOTICE:  table "unnest_2d_tbl01_out" does not exist, skipping
 -- The following CTAS fails previously, see Github Issue 9365
 CREATE TABLE unnest_2d_tbl01_out AS
   SELECT id, (array_unnest_2d_to_1d(val)).* FROM unnest_2d_tbl01;
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'id' as the Cloudberry Database 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.
 -- Github issue 9790.
 -- Previously, CTAS with no data won't handle the 'WITH' clause
 CREATE TABLE ctas_base(a int, b int);
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Cloudberry Database 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 ctas_aocs WITH (appendonly=true, orientation=column) AS SELECT * FROM ctas_base WITH NO DATA;
 NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause. Creating a NULL policy entry.
@@ -406,12 +401,10 @@ create or replace function mv_action_select_issue_11999() returns bool language
 create materialized view sro_mv_issue_11999 as select mv_action_select_issue_11999() with no data;
 INFO:  GPORCA failed to produce a plan, falling back to Postgres-based planner
 DETAIL:  Falling back to Postgres-based planner because GPORCA does not support the following feature: SIRV functions
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'mv_action_select_issue_11999' as the Cloudberry Database 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 t_sro_mv_issue_11999 as select mv_action_select_issue_11999() with no data;
 INFO:  GPORCA failed to produce a plan, falling back to Postgres-based planner
 DETAIL:  Falling back to Postgres-based planner because GPORCA does not support the following feature: SIRV functions
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named 'mv_action_select_issue_11999' as the Cloudberry Database 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 count(*)
 from
@@ -467,7 +460,6 @@ AS $function$declare cname refcursor = 'result'; begin open cname for select 1;
 SELECT exception_func() INTO TEMPORARY test_tmp1;
 INFO:  GPORCA failed to produce a plan, falling back to Postgres-based planner
 DETAIL:  Falling back to Postgres-based planner because GPORCA does not support the following feature: SIRV functions
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named '' as the Cloudberry Database 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 * FROM test_tmp1;
  exception_func 
@@ -478,7 +470,6 @@ SELECT * FROM test_tmp1;
 CREATE TEMPORARY TABLE test_tmp2 AS SELECT exception_func();
 INFO:  GPORCA failed to produce a plan, falling back to Postgres-based planner
 DETAIL:  Falling back to Postgres-based planner because GPORCA does not support the following feature: SIRV functions
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named '' as the Cloudberry Database 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 * FROM test_tmp2;
  exception_func 

src/test/regress/expected/select_into.out

@@ -214,7 +214,6 @@ LINE 1: INSERT INTO b SELECT 1 INTO f;
 -- Empty target list 
 --
 explain (costs off) select into empty_tl from generate_series(0, 10);
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named '' as the Cloudberry Database 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.
                    QUERY PLAN                   
 ------------------------------------------------
@@ -224,7 +223,6 @@ HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sur
 (3 rows)
 
 select into empty_tl from generate_series(0, 10);
-NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column(s) named '' as the Cloudberry Database 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 * from empty_tl;
 --