[BugFix] Fix InfoSchemaDb id increasing continuously bug

[gengjun-git]

trafficstars

What type of PR is this：

• [x] bug
• [ ] feature
• [ ] enhancement
• [ ] refactor
• [ ] others

Which issues of this PR fixes ：

Fixes #9810

Problem Summary(Required) ：

The information_schema db is not persisted, it is generated in loadCluster when loading image. Its id will increase once the loadCluster is called. If the cluster runs for a long time(3 months for example), its id may be bigger than 10000 ( which is the upper limit of system id), because the loadCluster will be called every time a checkpoint is done. The reason why the information_schema db's id will be increased maybe there will be many clusters in the system and every cluster will have its own information_schema db. But the cluster has be deprecated in our system, so we just give a fixed id number for every system db or table.

Checklist:

• [ ] I have added test cases for my bug fix or my new feature
• [ ] I have added user document for my new feature or new function

[wanpengfei-git]

run starrocks_admit_test

[gengjun-git]

run starrocks_fe_unittest

[gengjun-git]

run starrocks_fe_unittest

[wanpengfei-git]

run starrocks_admit_test

[wanpengfei-git]

run starrocks_admit_test

[wanpengfei-git]

run starrocks_admit_test

[sonarqubecloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

0.0% Coverage
0.0% Duplication

[wanpengfei-git]

[FE PR Coverage Check]

:disappointed: fail : 1 / 2 (50.00%)

file detail

	path	covered_line	new_line	coverage	not_covered_line_detail
:large_blue_circle:	com/starrocks/common/SystemId.java	0	1	00.00%	[7]
:large_blue_circle:	com/starrocks/catalog/InfoSchemaDb.java	1	1	100.00%	[]

[gengjun-git]

@mergify backport branch-2.4

[mergify[bot]]

backport branch-2.4

✅ Backports have been created

• #11494 [BugFix] Fix InfoSchemaDb id increasing continuously bug (backport #9811) has been created for branch branch-2.4