Sync release-material_ui-1.2.0 to main

[fluttergithubbot]

This automated PR syncs the changes from the release branch release-material_ui-1.2.0 back to the main branch.

[gemini-code-assist]

Code Review

This pull request bumps the version of the material_ui package to 1.2.0, updates the CHANGELOG.md with the release notes, and removes temporary changelog files. Feedback is provided to correct a grammatical inconsistency in one of the changelog entries to match the third-person singular present tense used in the other entries.

[gemini-code-assist]

For consistency with the other changelog entries in this release, please use the third-person singular present tense ("Fixes" instead of "Fix") and add a trailing period.

Suggested change

	- Fix RangeSlider thumb overlay remaining visible after touch interaction
	- Fixes RangeSlider thumb overlay remaining visible after touch interaction.

[QuncCccccc]

LGTM

[Piinks]

This ended up in conflict, I think it got out of order with last week's release and this week's. @chunhtai will this just fix itself on the next run?

[chunhtai]

the sync back need to land first before next release went out

otherwise, the change log will duplicate because those old entry is not cleaned up, but other than that it won't have any issue with the actual released code

[chunhtai]

if the bot can't create a compatible pr, you can also manually create a branch from release-material_ui-1.2.0 with some conflict resolution and merge it into main with the override: batch-material_ui label

[chunhtai]

once that is done, you can retrigger the batch release github action to generate a fresh release pr

[chunhtai]

let me adjust the ci to see if i can do something to avoid this situation

[fluttergithubbot]

An existing Git SHA, b3c3ac009e69d2843fcd98cff19bfde59ec3d913, was detected, and no actions were taken.

To re-trigger presubmits after closing or re-opeing a PR, or pushing a HEAD commit (i.e. with --force) that already was pushed before, push a blank commit (git commit --allow-empty -m "Trigger Build") or rebase to continue.