fix: use reflection for original StatusBar implementation discovery

[kirillzyusko]

📜 Description

Use reflection for StatusBarModule usage.

💡 Motivation and Context

It seems like in RN 0.80+ the StatusBarModule is internal now (kotlin). So we can't use ir directly anymore - moreover the usage of internal class will lead to compilation errors.

An ideal fix is to make it public again in react-native framework, but it'll take some time and some RN versions will still use internal modificator. So in order to assure better compatibility across different RN versions I decided to use reflection. We can not use the approach with Java's protected classes (where we create the same package name and export public wrapper), because kotlin has a stricter policy. So we have two options how to fix it:

• reflection
• copy-paste original code

We already use reflection in 2 places (though they will be removed in the future) I decided to add more usage and create StatusBarModuleProxy.

In this PR I also re-structured the fs and created statusbar folder where placed proxy + module implementations.

📢 Changelog

Android

• created StatusBarModuleProxy based on reflection;
• created statusbar folder;
• update imports that use StatusBarModuleCompat;

🤔 How Has This Been Tested?

Tested on Pixel 3A (API 33, emulator).

📸 Screenshots (if appropriate):

Screen.Recording.2025-07-06.at.15.23.20.mov

📝 Checklist

• CI successfully passed
• I added new mocks and corresponding unit-tests if library API was changed

[github-actions]

📊 Package size report

Current size	Target Size	Difference
207793 bytes	207238 bytes	555 bytes 📈