Epic: rename old names for ASF brand Compliance

[tuhaihe]

closes: #212

---

Change logs

This PR introduces several key updates to ensure ASF compliance, improve documentation quality, and align project names with Apache standards:

1. Rename old names for ASF brand compliance

• Rebranded all references from “Cloudberry Database” to “Apache Cloudberry” throughout the documentation.
• Ensured consistent naming for better clarity and adherence to ASF branding guidelines.

2. Fix broken anchors warnings in the documentation

• Resolved warnings caused by broken internal links and anchors in the docs.

3. Delete non-ASF release artifacts

• Removed legacy, non-ASF-compliant release content.

If you think we can keep them now, I can revert the changes, please let me know.

4. Update old GitHub URLs

• Replaced outdated GitHub repository URLs with the correct Apache-hosted project links.

Contributor's checklist

Here are some reminders before you submit your pull request:

• Make sure that your Pull Request has a clear title and commit message. You can take the Git commit template as a reference.
• Learn the code contribution and doc contribution guides for better collaboration.
• Make sure that your changes deployment preview is successful.
• List your communications in the GitHub Issues or Discussions (if has or needed).
• Feel free to ask for the cloudberry committers or other people to help review and approve.

[tuhaihe]

Will check the files again before merging them.

[TomShawn]

In /i18n/zh/docusaurus-plugin-content-docs/current/releases/release-1.5.3.md, modify the link in line 15 to /i18n/zh/docusaurus-plugin-content-docs/current/cbdb-linux-compile.md#第-4-步构建-apache-cloudberry.

In /Users/hashdata/Documents/GitHub/upstream-cloudberrydb-site/docs/releases/release-1.5.3.md, modify the link in line 21 to /docs/cbdb-linux-compile#step-4-build-apache-cloudberry.

[TomShawn]

In the release notes (both en and zh), the old name "Cloudberry Database" remains unchanged. Is that expected? Besides, you can still get many "Cloudberry Database" search results within this PR branch.

[tuhaihe]

In the release notes (both en and zh), the old name "Cloudberry Database" remains unchanged. Is that expected? Besides, you can still get many "Cloudberry Database" search results within this PR branch.

For pre-ASF releases, as they are not Apache releases, we cannot rename
them to Apache Cloudberry. We may consider deleting them after our first
Apache release , but for now, let's keep them unchanged.

As for other occurrences of "Cloudberry Database" outside the docs, I plan
to update them in a separate PR.

[TomShawn]

LGTM

[edespino]

There are many references to the following which should be updated throughout:

• The old repository name cloudberrydb (in various capitalization forms).
• cloudberrydb.org

[tuhaihe]

There are many references to the following which should be updated throughout:

• The old repository name cloudberrydb (in various capitalization forms).
• cloudberrydb.org

Done. Thanks for your feedback!
Hi @edespino, please take a look again, thanks!

Note: There are still a lot of old links like https://github.com/cloudberrydb/cloudberrydb-site/blob/cbdb-doc-validation/docs/sql-stmts/release-savepoint.md. This should be replaced with the new redirect links in the documentation and not included in this PR. I have already created the issue - #215 for tracking.