Make multiple_windows follow repo analyzer rules

[goderbauer]

The default analysis_options.yaml file created by flutter create was accidentally checked in for the multiple_windows example. It disables the repo-level analyzer rules. This deletes the custom file and adjusts the code to follow the global rules. All code fixes were implemented by Gemini.

[gemini-code-assist]

Code Review

This pull request refactors the multiple_windows example by removing the local analysis_options.yaml, reordering imports, and applying consistent formatting across the project. The changes introduce explicit type annotations for variables and constants, add const modifiers to various widgets, and simplify dialog implementations by removing unnecessary async keywords and default parameters. Review feedback focuses on maintaining consistent type annotations and explicit typing for dialog calls to comply with the repository's style guidelines.

[gemini-code-assist]

To adhere to the repository's coding standards (specifically the always_specify_types rule), please provide an explicit type for the controller variable.

Suggested change

	final controller =DialogWindowController(
	finalDialogWindowControllercontroller =DialogWindowController(

[goderbauer]

Not necessary, type is obvious from the right side.

[gemini-code-assist]

Please specify the explicit type for trackersCopy to follow the repository's style guide regarding type annotations.

Suggested change

	final trackersCopy =List<ElementPositionTracker>.from(_trackers, growable:false);
	finalList<ElementPositionTracker> trackersCopy =List<ElementPositionTracker>.from(_trackers, growable:false);

[goderbauer]

Not necessary, type is obvious from the right side.

[gemini-code-assist]

The always_specify_types rule is followed throughout this PR. Please add the explicit type for the tracker variable here for consistency.

Suggested change

	final tracker =ElementPositionTracker(element: _popupButtonKey.currentContext!);
	finalElementPositionTrackertracker =ElementPositionTracker(element: _popupButtonKey.currentContext!);

[goderbauer]

Not necessary, type is obvious from the right side.

[gemini-code-assist]

In the Flutter repository, it is preferred to explicitly specify types for constants. Please add int to these declarations.

Suggested change

	const lowerBound =32;
	const span =160;
	constintlowerBound =32;
	constintspan =160;

[goderbauer]

Not necessary, type is obvious from the right side.

[gemini-code-assist]

Please provide an explicit type for the tracker variable to maintain consistency with the repository's analyzer rules.

Suggested change

	final tracker =ElementPositionTracker(element: _tooltipButtonKey.currentContext!);
	finalElementPositionTrackertracker =ElementPositionTracker(element: _tooltipButtonKey.currentContext!);

[goderbauer]

Not necessary, type is obvious from the right side.

[gemini-code-assist]

The explicit type String was removed here, but the repository's style guide generally requires explicit types for all declarations. Please restore it.

Suggested change

	const windowingDisabledErrorMessage ='''
	constStringwindowingDisabledErrorMessage ='''

[goderbauer]

Not necessary, type is obvious from the right side.

[justinmc]

Thanks for catching this @goderbauer! I'm kind of embarrassed that I didn't notice any of these analyzer problems when I reviewed this, I guess I just rely on it to be there.