Release Version Using Alpha Dependency 'androidx.browser:browser:1.9.0-alpha04'

**Describe the bug**

Dependabot discovered the new android-browser-helper 2.6.x release. When running our different CI checks, we discovered that it pulls an alpha dependency `androidx.browser:browser:1.9.0-alpha04`.

**To Reproduce**

Check additional context below.

**Expected behavior**

We'd expect a release not pulling in an alpha release, especially one which requires API 36. There is no reference in the Release notes on this either.

**Did this ever used to work**

android-browser-helper 2.5.0 works well.

**Additional context**

Few failing workflows as an example:
- https://github.com/FusionAuth/fusionauth-android-sdk/actions/runs/15955672742/job/45001628707?pr=215#step:7:166
- https://github.com/FusionAuth/fusionauth-android-sdk/actions/runs/15955672742/job/45001628707?pr=215#step:6:285
- https://github.com/FusionAuth/fusionauth-android-sdk/actions/runs/15955672734/job/45001628711?pr=215#step:6:283

All with the error:

```
1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:checkReleaseAarMetadata'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.CheckAarMetadataWorkAction
> An issue was found when checking AAR metadata:

1. Dependency 'androidx.browser:browser:1.9.0-alpha04' requires libraries and applications that
depend on it to compile against version 36 or later of the
Android APIs.

:app is currently compiled against android-35.

Recommended action: Update this project to use a newer compileSdk
of at least 36, for example 36.

Note that updating a library or application's compileSdk (which
allows newer APIs to be used) can be done separately from updating
targetSdk (which opts the app in to new runtime behavior) and
minSdk (which determines which devices the app can be installed
on).
```