[AMORO-2802] Change the folder name of optimizer module

[zhongqishang]

Why are the changes needed?

Close #2802 .

Brief change log

• Add prefix amoro
• Keep the same with module and folder name

How was this patch tested?

• Add some test cases that check the changes thoroughly including negative and positive cases if possible

• Add screenshots for manual tests if appropriate

• Run test locally before making a pull request

Documentation

• Does this pull request introduce a new feature? (yes / no)
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

[xleoken]

lgtm

[zhoujinsong]

Hi,

We used to say Flink optimizer/Spark optimizer. So do you think amoro-flink-optimizer/amoro-spark-optimizer is a proper name for both the artifact id and the folder name?

[zhongqishang]

Hi,

We used to say Flink optimizer/Spark optimizer. So do you think amoro-flink-optimizer/amoro-spark-optimizer is a proper name for both the artifact id and the folder name?

@zhoujinsong @xleoken

Yes, we used to say Flink/Spark optimizer, in order to maintain the unity of the module format, I looked at the flink connector.
Like the structure of flink connector, the module name does not affect us calling it flink kafka connector[1].

[1] : https://github.com/apache/flink-connector-kafka

[xleoken]

hi @zhongqishang @zhoujinsong

We can keep the style as amoro-mixed-format module, so amoro-optimizer-flink and amoro-optimizer-spark is ok.

amoro-mixed-format

• amoro-mixed-format-flink
• amoro-mixed-format-hive
• amoro-mixed-format-spark
• amoro-mixed-format-trino

[zhoujinsong]

Make sense to me.