Button `disabled` unexpected behavior on Android

Description

On Android devices, the initial state of disabled for Button leads to unexpected behavior. When disabled is initially specified as true but later changes to false, the the background remains gray and disabled-like. This is unexpected behavior. This is not the case when disabled is initially specified as false.

Steps to reproduce

1. Check out https://snack.expo.dev/@ctnelson1997/button-reset?platform=android
2. Run on Android (Pixel 9 Pro used)
3. When useState has an initial value of 0, the app works as expected.
4. When useState has an initial value of 5, and the reset button is pressed, the button still appears disabled. This is unexpected behavior.

React Native Version

0.81.5

Affected Platforms

Runtime - Android

Output of npx @react-native-community/cli info

System:
  OS: Windows 11 10.0.22631
  CPU: (14) x64 Intel(R) Core(TM) Ultra 5 125U
  Memory: 2.98 GB / 15.46 GB
Binaries:
  Node:
    version: 22.19.0
    path: C:\Program Files\nodejs\node.EXE
  Yarn: Not Found
  npm:
    version: 10.9.3
    path: C:\Program Files\nodejs\npm.CMD
  Watchman: Not Found
SDKs:
  Android SDK: Not Found
  Windows SDK:
    AllowAllTrustedApps: Disabled
IDEs:
  Android Studio: Not Found
  Visual Studio: Not Found
Languages:
  Java:
    version: 21.0.5
    path: C:\Program Files\Eclipse Adoptium\jdk-21.0.5.11-hotspot\bin\javac.EXE
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 19.1.0
    wanted: 19.1.0
  react-native:
    installed: 0.81.5
    wanted: 0.81.5
  react-native-windows: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found

info React Native v0.82.1 is now available (your project is running on v0.81.5).
info Changelog: https://github.com/facebook/react-native/releases/tag/v0.82.1
info Diff: https://react-native-community.github.io/upgrade-helper/?from=0.81.5&to=0.82.1
info For more info, check out "https://reactnative.dev/docs/upgrading?os=windows".

Stacktrace or Logs

N/A, issue is visual.

MANDATORY Reproducer

https://snack.expo.dev/@ctnelson1997/button-reset?platform=android

Screenshots and Videos

Start by running the mandatory Snack reproducer on Android with the two initial useState values described in the issue, then trace the React Native Button Android implementation. Done means changing disabled from true to false after reset also removes the gray disabled appearance, while the existing false-to-false behavior remains unchanged; add regression coverage if the relevant test entry point is identified.