[CORE][umbrella] Configuration enhancements

[yikf]

Description

As discussed in #6970, we plan to enhance the gluten configuration, and the specific enhancement solutions can be found in section #6970 (comment).

This issue serves as an umbrella to record the task list that we need to include to achieve our goals, because enhance config involves a large number of files, splitting multiple tasks facilitates code review and reduces the risk of introducing other problems.

• [CORE] Introduce the ConfigEntry to make the config definition more flexible #8327
  This task involves a large number of files. Due to the performance regressions of the CH backend, we refined this task into three parts:

1. [GLUTEN-8327][CORE][Part-1] Rename GlutenConfig.getConf to GlutenConfig.get #8395
2. [GLUTEN-8327][CORE][Part-2] Move GlutenConfig.scala to org.apache.gluten.config package dir  #8426
3. [GLUTEN-8327][CORE][Part-3] Introduce the ConfigEntry to gluten config #8431

• Split the configuration into individual modules that belong to each other.
• Split configuration into two separate files: one static and one non-static.
• Standardize configuration naming, log the deprecated config name if used.
• [CORE] Support generate configurations golden file and check it  #8070

[baibaichen]

@yikf as discussed in the offline, there are 2 requirement

1. Pass spark config to backend. For example, ch backend need spark.sql.caseSensitive to choose compare behavior.
2. Pass value type to backend. currently we use ConfigMap which assum value is string type.