[material_ui] Remove unconditional dart:io import from about.dart

[Gyeony95]

about.dart imported dart:io unconditionally, only to read Platform.resolvedExecutable as the fallback application name when no Title ancestor is found. Because about.dart is reachable from the material_ui barrel, pana 0.23.18's static platform analysis marks the whole package as not supporting the web, which drops the platform:web and is:wasm-ready tags on pub.dev. It also means that fallback path throws UnsupportedError when it is actually reached on the web.

This PR moves the executable-name lookup behind a conditional import (_about_io.dart / _about_web.dart), following the same pattern package:flutter's foundation library uses for _platform_io.dart / _platform_web.dart. On the web the fallback name is the empty string, matching the existing empty-string default for the application version. The [Platform.resolvedExecutable] doc references are kept resolvable with a @docImport.

Verified locally with pana 0.23.x on this branch: Supports 6 of 6 possible platforms, and the platform:web / is:wasm-ready tags are back.

Fixes flutter/flutter#191887

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the AI contribution guidelines and understand my responsibilities, or I am not using AI tools.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I followed the version and CHANGELOG instructions, using semantic versioning and the repository CHANGELOG style, or I have commented below to indicate which documented exception this PR falls under¹.
• I updated/added any relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or I have commented below to indicate which test exemption this PR falls under¹.
• All existing and new tests are passing.

Footnotes

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. ↩ ↩²

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[gemini-code-assist]

Code Review

This pull request refactors AboutDialog to remove the unconditional dart:io import, using conditional imports (_about_io.dart and _about_web.dart) to resolve the executable name on web and native platforms. It also adds tests to verify this behavior. The review feedback points out that the test file itself introduces an unconditional dart:io import and accesses Platform.resolvedExecutable, which will cause compilation failures during web testing, and suggests applying conditional imports to the test file as well.

[gemini-code-assist]

Unconditionally importing dart:io in a test file will cause compilation failures when running tests on the web (e.g., via flutter test --platform chrome). Since this PR aims to enable web support, we should avoid unconditional dart:io imports in the test file as well. We can use a conditional import to import the platform-specific executable name helper instead.

Suggested change

	import 'dart:io' show Platform;
	import 'package:material_ui/src/_about_io.dart'
	if (dart.library.js_interop) 'package:material_ui/src/_about_web.dart' as about;

[Gyeony95]

dart:io compiles on the web (it just throws at runtime), so an unconditional import in a test file does not break web test compilation. This file passes with flutter test --platform chrome as-is, and the only test that touches Platform is skipped on the web with skip: kIsWeb. Other tests in this repo (e.g. test/l10n/translations_test.dart) import dart:io the same way. Importing src/_about_io.dart from a test would also couple the test to a private implementation file, so I would prefer to keep the plain import.

[gemini-code-assist]

Use the conditionally imported about.executableName instead of directly accessing Platform.resolvedExecutable to avoid the compile-time dependency on dart:io on the web.

Suggested change

	final String expectedName = Platform.resolvedExecutable.split(Platform.pathSeparator).last;
	final String expectedName = about.executableName;

[Gyeony95]

Computing the expected value from Platform.resolvedExecutable directly is intentional: the widget already reads about.executableName, so using the same getter as the expected value would just compare the getter against itself. Deriving it independently keeps the test meaningful. This test is skipped on the web (skip: kIsWeb), so there is no dart:io runtime dependency there.