[mustache_template] Emoji support (flutter#10110)

Support emojis in templates. The code was relying on String.length, when doing substring, which could be wrong when emojis are used.

Fixes flutter/flutter#176180

## Pre-Review Checklist

**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.

[image_picker] Fix typos in error messages for platform interface (fl…

…utter#10211)

A part split from flutter#10188.

## Pre-Review Checklist

[^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.

[go_router] Support for top level `onEnter` callback. (flutter#8339)

**Description:**  
This PR introduces top level `onEnter` callback in `RouteConfiguration` to allow developers to intercept and conditionally block navigation based on incoming routes. It adds an example (`top_level_on_enter.dart`) demonstrating its usage, such as handling referral code from `/referral`.

**What This PR Changes:**  

- Adds the `onEnter` callback (`typedef OnEnter`) to intercept route navigation before processing.
- Implements logic for `onEnter` in `GoRouteInformationParser`.
- Updates `RouteConfiguration` to include the `onEnter` callback.
- Adds a new example, `top_level_on_enter.dart`, to demonstrate the feature.
- Adds a test case to verify the `onEnter` callback functionality.

**Simple usage example:**
```
final GoRouter router = GoRouter(
  onEnter: (context, state) {
    // Save the referral code (if provided) and block navigation to /referral.
    if (state.uri.path == '/referral') {
      saveReferralCode(context, state.uri.queryParameters['code']);
      return false;
    }

    return true; // Allow navigation for all other routes.
  },
  routes: [ ... ],
);
```

**Impact:**  
Enables developers to implement route-specific logic, such as support for handling action-based deep links without navigation ([160602](flutter/flutter#160602))

[various] Migrate example Radio groups to new RadioGroup API (flutter…

…#10155)

This PR updates multiple package **example** apps to stop using deprecated `groupValue` and `onChanged` on individual `Radio` widgets and instead use the new `RadioGroup<T>` ancestor to manage the selected value and change handling.

### Why  
Flutter deprecated `Radio.groupValue` and `Radio.onChanged` in favor of `RadioGroup`, which centralizes selection state for related radios. The deprecation is currently reported across several examples in this repo (see linked issue for examples and affected packages). This PR resolves those warnings.

### What changed (pattern applied across examples)  
- Wrap related `Radio<T>` widgets in a `RadioGroup<T>(groupValue: ..., onChanged: ...)`.  
- Remove `groupValue`/`onChanged` from each `Radio`, leaving only `value` (+ its label UI).  
  - Example (from `animations` demo): old three `Radio` widgets each had `groupValue`/`onChanged`; now they are enclosed in a single `RadioGroup<SharedAxisTransitionType>` and the `Radio` children keep just their `value`.

### Packages (examples) updated  
- `animations`  
- `camera`  
- `camera_android`  
- `camera_android_camerax`  
- `camera_avfoundation`  
- `google_sign_in_web`  
- `two_dimensional_scrollables` (both `table_view` and `tree_view`)  

### Screenshots  
N/A (UI unchanged; only wiring of radios changed).

### Links  
Fixes: [flutter/flutter#170915](flutter/flutter#170915)

---

## Pre-Review Checklist

[various] Migrate example Radio groups to new RadioGroup API (flutter…

…#10155)

This PR updates multiple package **example** apps to stop using deprecated `groupValue` and `onChanged` on individual `Radio` widgets and instead use the new `RadioGroup<T>` ancestor to manage the selected value and change handling.

### Why  
Flutter deprecated `Radio.groupValue` and `Radio.onChanged` in favor of `RadioGroup`, which centralizes selection state for related radios. The deprecation is currently reported across several examples in this repo (see linked issue for examples and affected packages). This PR resolves those warnings.

### What changed (pattern applied across examples)  
- Wrap related `Radio<T>` widgets in a `RadioGroup<T>(groupValue: ..., onChanged: ...)`.  
- Remove `groupValue`/`onChanged` from each `Radio`, leaving only `value` (+ its label UI).  
  - Example (from `animations` demo): old three `Radio` widgets each had `groupValue`/`onChanged`; now they are enclosed in a single `RadioGroup<SharedAxisTransitionType>` and the `Radio` children keep just their `value`.

### Packages (examples) updated  
- `animations`  
- `camera`  
- `camera_android`  
- `camera_android_camerax`  
- `camera_avfoundation`  
- `google_sign_in_web`  
- `two_dimensional_scrollables` (both `table_view` and `tree_view`)  

### Screenshots  
N/A (UI unchanged; only wiring of radios changed).

### Links  
Fixes: [flutter/flutter#170915](flutter/flutter#170915)

---

## Pre-Review Checklist

[various] Migrate example Radio groups to new RadioGroup API (flutter…

…#10155)

This PR updates multiple package **example** apps to stop using deprecated `groupValue` and `onChanged` on individual `Radio` widgets and instead use the new `RadioGroup<T>` ancestor to manage the selected value and change handling.

### Why  
Flutter deprecated `Radio.groupValue` and `Radio.onChanged` in favor of `RadioGroup`, which centralizes selection state for related radios. The deprecation is currently reported across several examples in this repo (see linked issue for examples and affected packages). This PR resolves those warnings.

### What changed (pattern applied across examples)  
- Wrap related `Radio<T>` widgets in a `RadioGroup<T>(groupValue: ..., onChanged: ...)`.  
- Remove `groupValue`/`onChanged` from each `Radio`, leaving only `value` (+ its label UI).  
  - Example (from `animations` demo): old three `Radio` widgets each had `groupValue`/`onChanged`; now they are enclosed in a single `RadioGroup<SharedAxisTransitionType>` and the `Radio` children keep just their `value`.

### Packages (examples) updated  
- `animations`  
- `camera`  
- `camera_android`  
- `camera_android_camerax`  
- `camera_avfoundation`  
- `google_sign_in_web`  
- `two_dimensional_scrollables` (both `table_view` and `tree_view`)  

### Screenshots  
N/A (UI unchanged; only wiring of radios changed).

### Links  
Fixes: [flutter/flutter#170915](flutter/flutter#170915)

---

## Pre-Review Checklist

[various] Migrate example Radio groups to new RadioGroup API (flutter…

…#10155)

This PR updates multiple package **example** apps to stop using deprecated `groupValue` and `onChanged` on individual `Radio` widgets and instead use the new `RadioGroup<T>` ancestor to manage the selected value and change handling.

### Why  
Flutter deprecated `Radio.groupValue` and `Radio.onChanged` in favor of `RadioGroup`, which centralizes selection state for related radios. The deprecation is currently reported across several examples in this repo (see linked issue for examples and affected packages). This PR resolves those warnings.

### What changed (pattern applied across examples)  
- Wrap related `Radio<T>` widgets in a `RadioGroup<T>(groupValue: ..., onChanged: ...)`.  
- Remove `groupValue`/`onChanged` from each `Radio`, leaving only `value` (+ its label UI).  
  - Example (from `animations` demo): old three `Radio` widgets each had `groupValue`/`onChanged`; now they are enclosed in a single `RadioGroup<SharedAxisTransitionType>` and the `Radio` children keep just their `value`.

### Packages (examples) updated  
- `animations`  
- `camera`  
- `camera_android`  
- `camera_android_camerax`  
- `camera_avfoundation`  
- `google_sign_in_web`  
- `two_dimensional_scrollables` (both `table_view` and `tree_view`)  

### Screenshots  
N/A (UI unchanged; only wiring of radios changed).

### Links  
Fixes: [flutter/flutter#170915](flutter/flutter#170915)

---

## Pre-Review Checklist

[go_router_builder] expand supported versions of analyzer, build and …

…source_gen (flutter#10078)

close flutter/flutter#175071

Expand support [build](https://pub.dev/packages/build) and [source_gen](https://pub.dev/packages/source_gen) versions to support build v4 and source_gen v4
Expand support [analyzer](https://pub.dev/packages/analyzer) version to allow to v8.

*List which issues are fixed by this PR. You must list at least one issue.*

## Pre-Review Checklist

**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.

[camera_avfoundation] Wrappers swift migration - part 1 (flutter#10119)

Migrates camera wrappers as part of flutter/flutter#119109

This PR migrates wrappers to Swift:
* `FLTCamConfiguration`
* `FLTCamMediaSettingsAVWrapper`
* `FLTCaptureOutput`
* `FLTCapturePhotoOutput`
* `FLTCaptureVideoDataOutput`

In line with Swift conventions, the `FLT` prefixes are removed. The `Default` class implementations are replaced with protocol conformance on base `AV` classes.

## Pre-Review Checklist

**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.

[dependabot]: Bump camerax_version from 1.5.0 to 1.5.1 in /packages/c…

…amera/camera_android_camerax/android (flutter#10220)

Bumps `camerax_version` from 1.5.0 to 1.5.1.
Updates `androidx.camera:camera-core` from 1.5.0 to 1.5.1

Updates `androidx.camera:camera-camera2` from 1.5.0 to 1.5.1

Updates `androidx.camera:camera-lifecycle` from 1.5.0 to 1.5.1

Updates `androidx.camera:camera-video` from 1.5.0 to 1.5.1

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>