[BugFix] fix mem leak when caching mv plan context (backport #72300)

[mergify]

Why I'm doing:

There are lots of LakeTablet object on FOLLOWER after frequently drop&create same materialized view.
And objects can't be releazed after fe transfers to LEADER.

 num     #instances         #bytes  class name (module)
-------------------------------------------------------
   1:      24469095     1080226352  [B (java.base@17.0.2)
   2:      13197226     1055778080  com.starrocks.lake.LakeTablet

What I'm doing:

Removed dropped materialized view object from pending cache and double check materialized view still exists before be added to context cache.

Fixes #issue

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.

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 pr needs auto generate documentation
• 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
  • 4.1
  • 4.0
  • 3.5
  • 3.4

---

This is an automatic backport of pull request #72300 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 33ccc4a has failed:

On branch mergify/bp/branch-3.5/pr-72300
Your branch is up to date with 'origin/branch-3.5'.

You are currently cherry-picking commit 33ccc4ae03.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   fe/fe-core/src/main/java/com/starrocks/sql/optimizer/CachingMvPlanContextBuilder.java

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   fe/fe-core/src/test/java/com/starrocks/planner/MaterializedViewTextBasedRewriteTest.java

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[mergify]

@mergify[bot]: Backport conflict, please reslove the conflict and resubmit the pr

[kevincai]

@copilot fix the backport conflict in single commit, don't edit pull request description.

[Copilot]

@copilot fix the backport conflict in single commit, don't edit pull request description.

Fixed in single amended commit c91a848e. I resolved the backport conflict in MaterializedViewTextBasedRewriteTest and left the PR description unchanged.

[trueeyu]

@mergify backport branch-3.5-cc

[mergify]

backport branch-3.5-cc

✅ Backports have been created

Details

• #73091 [BugFix] fix mem leak when caching mv plan context (backport #72300) (backport #72389) has been created for branch branch-3.5-cc