Roll Engine from c176d6fb06cd to 4fbff7a5114a (2 revisions) - #100587

…lutter/flutter#100587)

…lutter/flutter#100587)

…lutter/flutter#100587)

…lutter/flutter#100587)

…lutter/flutter#100587)

…lutter/flutter#100587)

…lutter/flutter#100587)

…lutter/flutter#100587)

…lutter/flutter#100587)

…lutter/flutter#100587)

…lutter/flutter#100587)

…a_table_test, floating_action_button_test, text_field_cursor_test (#13460)

Removes web skips from three `material_ui` test files whose tests now pass on Chrome under both web renderers used in CI (CanvasKit/dart2js and Skwasm/dart2wasm). Keeping the skips hides web regressions in these widgets.

- `data_table_test.dart`: removes the file-level `@TestOn('!chrome')`. The column/cell padding finders now use `'${6.0}'` instead of `'6.0'`, so they match the text on dart2js (JS prints doubles with no fractional part as `6`, not `6.0`). Only the M3 `InkSparkle` press test stays skipped on web (flutter/flutter#100587).
- `floating_action_button_test.dart`: removes the file-level `@TestOn('!chrome')`, which turns 43 tests back on for web. The two ink splash clipping tests stay skipped on web (flutter/flutter#20483).
- `text_field_cursor_test.dart`: removes the file-level `@TestOn('!chrome')`. All 9 cursor animation, timing, and platform radius variants pass on web.

Verified locally with `flutter test --platform chrome` and `flutter test --platform chrome --wasm` for each file.

Part of flutter/flutter#100587
Part of flutter/flutter#20483

## Pre-Review Checklist

This PR only changes tests, so it is exempt from version/CHANGELOG updates and from the new-test requirement.

**Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). 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.

[^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.