[Enhancement] optimize the performance of refreshExternalTable stage of MV refresh

[murphyatwork]

Why I'm doing:

For MV on DataLake, MetadataMgr::refreshTable call can be costly if the external table has a lot of partitions.

To optimize it, we can optimize that call into a MetadataMgr::refreshTable(partitionNames), so we don't need to refresh all partitions each time.

Experimental result:

• For 10000 Hive partitions
• Before: the MetadataMgr.refreshTable takes 1.8s
• After: the MetadataMgr.refreshTable takes 60ms

What I'm doing:

Fixes #issue

What type of PR is this:

• [ ] BugFix
• [ ] Feature
• [x] Enhancement
• [ ] Refactor
• [ ] UT
• [ ] Doc
• [ ] Tool

Does this PR entail a change in behavior?

• [ ] Yes, this PR will result in a change in behavior.
• [x] 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:

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

[sonarcloud[bot]]

Quality Gate passed

Issues
5 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 SonarCloud

[github-actions[bot]]

[FE Incremental Coverage Report]

:white_check_mark: pass : 55 / 61 (90.16%)

file detail

	path	covered_line	new_line	coverage	not_covered_line_detail
:large_blue_circle:	com/starrocks/scheduler/mv/MVPCTRefreshListPartitioner.java	1	3	33.33%	[280, 281]
:large_blue_circle:	com/starrocks/scheduler/TableSnapshotInfo.java	6	8	75.00%	[79, 82]
:large_blue_circle:	com/starrocks/scheduler/PartitionBasedMvRefreshProcessor.java	39	41	95.12%	[256, 259]
:large_blue_circle:	com/starrocks/common/Config.java	1	1	100.00%	[]
:large_blue_circle:	com/starrocks/scheduler/mv/MVPCTRefreshRangePartitioner.java	8	8	100.00%	[]

[github-actions[bot]]

[BE Incremental Coverage Report]

:white_check_mark: pass : 0 / 0 (0%)

[github-actions[bot]]

@Mergifyio backport branch-3.3

[github-actions[bot]]

@Mergifyio backport branch-3.2

[github-actions[bot]]

@Mergifyio backport branch-3.1

[mergify[bot]]

backport branch-3.3

✅ Backports have been created

* [#47989 [Enhancement] optimize the performance of refreshExternalTable stage of MV refresh (backport #47809)](https://github.com/StarRocks/starrocks/pull/47989) has been created for branch `branch-3.3`

[mergify[bot]]

backport branch-3.2

✅ Backports have been created

* [#47990 [Enhancement] optimize the performance of refreshExternalTable stage of MV refresh (backport #47809)](https://github.com/StarRocks/starrocks/pull/47990) has been created for branch `branch-3.2` but encountered conflicts

[mergify[bot]]

backport branch-3.1

✅ Backports have been created

* [#47992 [Enhancement] optimize the performance of refreshExternalTable stage of MV refresh (backport #47809)](https://github.com/StarRocks/starrocks/pull/47992) has been created for branch `branch-3.1` but encountered conflicts