Migrate to WidgetPropertyResolver

[ValentinVignal]

Follow up of #175396

Migrate the remaining files from MaterialPropertyResolver to WidgetPropertyResolver. This PR only focus on WidgetPropertyResolver.

• This minimizes conflicts and reduces the size of the PR for easier reviews and follow up
• I'll work on the other elements of packages/flutter/lib/src/material/material_state.dart into other PRs

Pre-launch Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the Tree Hygiene wiki page, which explains my responsibilities.
• I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
• I signed the CLA.
• I listed at least one issue that this PR fixes in the description above.
• I updated/added relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or this PR is test-exempt.
• I followed the breaking change policy and added Data Driven Fixes where supported.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

[gemini-code-assist]

Code Review

This pull request correctly migrates usages of the deprecated MaterialPropertyResolver to WidgetPropertyResolver. The changes are straightforward and align with the goal of modernizing the API. I have one suggestion to improve the robustness of the _MouseCursor implementation in button_style_button.dart to prevent potential runtime errors.

[gemini-code-assist]

While this change is correct, the resolve method in the _MouseCursor class (line 624) uses a null-check operator (!). This could lead to a runtime error if a custom button implementation doesn't provide a mouseCursor style, causing resolveCallback to return null.

For improved robustness and consistency with _MouseCursor in menu_anchor.dart, it would be safer to provide a fallback value.

Consider changing line 624 from:

MouseCursor resolve(Set<WidgetState> states) => resolveCallback(states)!;

To:

MouseCursor resolve(Set<WidgetState> states) => resolveCallback(states) ?? MouseCursor.uncontrolled;

[QuncCccccc]

LGTM:)

[justinmc]

LGTM 👍