[brightness] rename method to prevent violating Rules of Hooks

[Simek]

Why

Fixes ENG-1738

How

Deprecate useSystemBrightnessAsync and add it as renamed restoreSystemBrightnessAsync method to avoid violating Rules of Hooks.

Test Plan

The changes have been tested by running docs website and NCL app locally in emulator.

Preview

Checklist

• Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md).
• Conforms with the Documentation Writing Style Guide
• This diff will work correctly for expo prebuild & EAS Build (eg: updated a module plugin).

[linear]

ENG-1738 [brightness] Rename `useSystemBrightnessAsync`

Current name (starting with use) causes ESLint and API Auto-Gen to interpreter this method as hook, which it isn't. It also violates the rules of hooks:

• https://github.com/expo/expo/blob/master/packages/expo-brightness/src/Brightness.ts#L110:L121

New name proposal:

• resetToSystemBrightnessAsync
• restoreSystemBrightnessAsync

[amandeepmittal]

Thanks for these changes! 🚀

[tsapeta]

You'll probably need to rebase it and fix the changelog entry. If you want this patch to be published for SDK 47, you would need to revert native changes and rename the function only on the JS side 😉