[various] Set cmake_policy versions (flutter#3828)

Use of `FetchContent` with default policy settings has a warning starting with CMake 3.24. This opts those plugins into new behaviors for everything up through 3.24 to avoid those warnings.

The `VERSION` is used rather than an explicity policy setting since this is the approach recommended by CMake docs. For any policies that we aren't currently hitting, we would want new behavior by default in the future so that we don't accidentally depend on deprecated behavior.

See flutter/flutter#116866

[various] Set cmake_policy versions (flutter#3828)

Use of `FetchContent` with default policy settings has a warning starting with CMake 3.24. This opts those plugins into new behaviors for everything up through 3.24 to avoid those warnings.

The `VERSION` is used rather than an explicity policy setting since this is the approach recommended by CMake docs. For any policies that we aren't currently hitting, we would want new behavior by default in the future so that we don't accidentally depend on deprecated behavior.

See flutter/flutter#116866

[various] Add `targetCompatibility` to build.gradle (flutter#3825)

While current docs about `targetCompatibility` say that it defaults to `sourceCompatibility`, for older toolchains (AGP?) that is apparently not the case, and it's a build error to set `sourceCompatibility` without `targetCompatibility`.

This adds enforcement that it's set to `gradle-check`, and fixes all of the violations.

Fixes flutter/flutter#125482

[path_provider] Allow `win32` up to version 4.x (flutter#3820)

Adds compatibility with version 4.x of `win32`. No breaking changes impacted the plugin, so this just relaxes the constraint.

Fixes flutter/flutter#125355

[various] Set cmake_policy versions (flutter#3828)

Use of `FetchContent` with default policy settings has a warning starting with CMake 3.24. This opts those plugins into new behaviors for everything up through 3.24 to avoid those warnings.

The `VERSION` is used rather than an explicity policy setting since this is the approach recommended by CMake docs. For any policies that we aren't currently hitting, we would want new behavior by default in the future so that we don't accidentally depend on deprecated behavior.

See flutter/flutter#116866

[various] Add `targetCompatibility` to build.gradle (flutter#3825)

While current docs about `targetCompatibility` say that it defaults to `sourceCompatibility`, for older toolchains (AGP?) that is apparently not the case, and it's a build error to set `sourceCompatibility` without `targetCompatibility`.

This adds enforcement that it's set to `gradle-check`, and fixes all of the violations.

Fixes flutter/flutter#125482

[various] Add `targetCompatibility` to build.gradle (flutter#3825)

While current docs about `targetCompatibility` say that it defaults to `sourceCompatibility`, for older toolchains (AGP?) that is apparently not the case, and it's a build error to set `sourceCompatibility` without `targetCompatibility`.

This adds enforcement that it's set to `gradle-check`, and fixes all of the violations.

Fixes flutter/flutter#125482

[various] Add `targetCompatibility` to build.gradle (flutter#3825)

While current docs about `targetCompatibility` say that it defaults to `sourceCompatibility`, for older toolchains (AGP?) that is apparently not the case, and it's a build error to set `sourceCompatibility` without `targetCompatibility`.

This adds enforcement that it's set to `gradle-check`, and fixes all of the violations.

Fixes flutter/flutter#125482

[various] Set cmake_policy versions (flutter#3828)

Use of `FetchContent` with default policy settings has a warning starting with CMake 3.24. This opts those plugins into new behaviors for everything up through 3.24 to avoid those warnings.

The `VERSION` is used rather than an explicity policy setting since this is the approach recommended by CMake docs. For any policies that we aren't currently hitting, we would want new behavior by default in the future so that we don't accidentally depend on deprecated behavior.

See flutter/flutter#116866

[various] Set cmake_policy versions (flutter#3828)

Use of `FetchContent` with default policy settings has a warning starting with CMake 3.24. This opts those plugins into new behaviors for everything up through 3.24 to avoid those warnings.

The `VERSION` is used rather than an explicity policy setting since this is the approach recommended by CMake docs. For any policies that we aren't currently hitting, we would want new behavior by default in the future so that we don't accidentally depend on deprecated behavior.

See flutter/flutter#116866