Revert "Build: use content hash for facebook-react-native build"

[kassens]

Reverts #27577.

We also sync React Native OSS bundles which means this didn't work as hoped unless we abandon the commit hash in OSS which seems useful.

[react-sizebot]

Comparing: 51ffd35...0acd3c6

Critical size changes

Includes critical production bundles, as well as any change greater than 2%:

Name	+/-	Base	Current	+/- gzip	Base gzip	Current gzip
oss-stable/react-dom/cjs/react-dom.production.min.js	=	175.04 kB	175.04 kB	=	54.47 kB	54.47 kB
oss-experimental/react-dom/cjs/react-dom.production.min.js	=	177.17 kB	177.17 kB	=	55.15 kB	55.15 kB
facebook-www/ReactDOM-prod.classic.js	=	567.61 kB	567.61 kB	=	99.94 kB	99.94 kB
facebook-www/ReactDOM-prod.modern.js	=	551.47 kB	551.47 kB	=	97.04 kB	97.04 kB

Significant size changes

Includes any change greater than 0.2%:

(No significant changes)

Generated by 🚫 dangerJS against 0acd3c6

[devichand1319]

I've noticed a change in the behavior of the fitBounds function in Leaflet, particularly when using the padding option. This change seems to have occurred since the RC1 release. In earlier versions, such as 0.7.5, the padding worked differently, but in newer versions like 1.0.0-rc.1, the padding appears to be much larger, causing the map to zoom out significantly.

I've also observed this issue when applying the padding to layers containing SVG polygons. Even with very small points, like L.point(0.001, 0.001), the map still zooms out excessively.

This seems like a regression in the fitBounds function, especially from RC1 onward. To address this issue, I would recommend reporting it to the Leaflet project's issue tracker or community forums, as it appears to be an unintended behavior or bug in the library.