build(#178): 构建多平台镜像

[861752346]

• 使用 Docker Buildx 构建多架构镜像（amd64 和 arm64）
• 更新基础镜像为 OpenEuler 24.03
• 移除 wgetLatestJdk.sh 和 wgetLatestJdk17.sh 脚本- 更新 Java 17镜像构建方式
• 优化 Doris 镜像构建，支持 noavx2 选项- 更新 Elasticsearch、HDFS、Kafka、SeaTunnel 和 Zookeeper 镜像的构建脚本

Closes #178

What is the purpose of the change

Add multi images support

Brief changelog

• Build multi-architecture images (amd64 and arm64) using Docker Buildx
• Update the base image to OpenEuler 24.03
• Remove the wgetLatestJdk.sh and wgetLatestJdk17.sh scripts - Update the Java 17 image building method
• Optimize the Doris image building process, supporting the noavx2 option - Update the building scripts for Elasticsearch, HDFS, Kafka, SeaTunnel and Zookeeper images

Verifying this change

[[Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 3 checklist before request the community to review your PR.

• Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Follow the git commit specification

  • feat: xxx -> The feat type is used to identify production changes related to new backward-compatible abilities or functionality.

  • perf: xxx -> The perf type is used to identify production changes related to backward-compatible performance improvements.

  • fix: xxx -> The fix type is used to identify production changes related to backward-compatible bug fixes.

  • docs: xxx -> The docs type is used to identify documentation changes related to the project - whether intended externally for the end users (in case of a library) or internally for the developers.

  • test: xxx -> The test type is used to identify development changes related to tests - such as refactoring existing tests or adding new tests.

  • refactor: xxx -> The refactor type is used to identify development changes related to modifying the codebase, which neither adds a feature nor fixes a bug - such as removing redundant code, simplifying the code, renaming variables, etc.

              ](https://github.com/dromara/CloudEon/issues/178)](https://github.com/dromara/CloudEon/issues/178)
    

[xlostpath]

你好，我是谢晋峰，你的邮件我已经收到，谢谢！