[Enhancement] Support persistent configuration

[crossoverJie]

Why I'm doing:

What I'm doing:

Fixes #52374

Using ADMIN SET FRONTEND CONFIG ("key" = "value") WITH PERSISTENT; to persist the configuration.
When restarting FE, these configurations still take effect.

This feature is only effective when the configuration file has write permissions in a virtual machine environment (it cannot be used in a container environment).

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• Yes, this PR will result in a change in behavior.
• No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• Interface/UI changes: syntax, type conversion, expression evaluation, display information
• Parameter changes: default values, similar parameters but with different default values
• Policy changes: use new policy to replace old one, functionality automatically enabled
• Feature removed
• Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• I have added test cases for my bug fix or my new feature
• This pr needs user documentation (for new or modified features or behaviors)
  • I have added documentation for my new feature or new function
• This is a backport pr

Bugfix cherry-pick branch check:

• I have checked the version labels which the pr will be auto-backported to the target branch
  • 3.4
  • 3.3
  • 3.2
  • 3.1
  • 3.0

[Samrose-Ahmed]

Perhaps you can explain your approach in case I don't understand, I dont think this is a good approach to check if in container and writing to files. Can't we use a different approach like persisiting to Starrocks meta?

[crossoverJie]

Perhaps you can explain your approach in case I don't understand, I dont think this is a good approach to check if in container and writing to files. Can't we use a different approach like persisiting to Starrocks meta?

Sorry for not explaining the background clearly.

In the k8s environment, users maintain configuration files using configmap, and each upgrade causes the configuration to be overwritten. Therefore, it has been decided to temporarily support configuration file persistence only in virtual machine environments.

The above background has been agreed upon with @kevincai @gengjun-git .

[github-actions]

[FE Incremental Coverage Report]

❌ fail : 52 / 78 (66.67%)

file detail

	path	covered_line	new_line	coverage	not_covered_line_detail
🔵	com/starrocks/server/NodeMgr.java	5	26	19.23%	[1165, 1166, 1168, 1173, 1174, 1175, 1176, 1177, 1179, 1181, 1183, 1184, 1185, 1186, 1187, 1188, 1190, 1192, 1193, 1194, 1196]
🔵	com/starrocks/common/ConfigBase.java	41	46	89.13%	[324, 325, 326, 331, 332]
🔵	com/starrocks/sql/ast/AdminSetConfigStmt.java	3	3	100.00%	[]
🔵	com/starrocks/service/FrontendServiceImpl.java	2	2	100.00%	[]
🔵	com/starrocks/common/util/Util.java	1	1	100.00%	[]

[sonarqubecloud]

Quality Gate passed

Issues
14 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

[Java-Extensions Incremental Coverage Report]

✅ pass : 0 / 0 (0%)

[github-actions]

[BE Incremental Coverage Report]

✅ pass : 0 / 0 (0%)