Automatically generate node support functions in cloudberry

[chenjinbao1989]

When merging Postgres 16, automatic generation of node support
functions was not enabled. This commit enables the automatic
generation of write, read, copy, and equal functions.

In future code, developers will no longer need to manually create
NodeTags and their corresponding write/read/copy/equal functions
when creating or modifying structures.

[tuhaihe]

The new file now includes the standard ASF license header and has passed the RAT scan. It looks fine to me. Thanks!

[tuhaihe]

Hi @chenjinbao1989 welcome to add the issue description to your commit message body for a better context.

You can take the .gitmessage as a commit template.

[chenjinbao1989]

Hi @chenjinbao1989 welcome to add the issue description to your commit message body for a better context.

You can take the .gitmessage as a commit template.

This pr does not come from a issue. It is a feature from pg16.

[tuhaihe]

Hi @chenjinbao1989 welcome to add the issue description to your commit message body for a better context.
You can take the .gitmessage as a commit template.

This pr does not come from a issue. It is a feature from pg16.

Thanks for the clarification!

That's totally fine. My point wasn't necessarily about having an issue, but about providing enough context in the commit message.

For PostgreSQL merge work, adding the upstream background or the related PostgreSQL commit in the message body would make the history much easier to understand later.

[tuhaihe]

If no more comments, could we start to merge this PR for PG16 FIXME?