fix(Android): prevent crash with InsetsObserverProxy already registered

[kkafar]

Description

Activity restarts do not invalidate JVM state entirely (at least it seems so), therefore InsetsObserverProxy
kept being registered on some decorview between activity restarts (context recreations) leading to crash
(we guard against multiple registrations).

Fixes #2519
Possibly fixes #2507

Changes

InsetsOberverProxy row registers for context lifecycle, when it's destroyed it cleans its state.

Test code and steps to reproduce

Haven't managed to reproduce this myself, but got confirmation in #2507 that this patch works.

Checklist

• Included code example that can be used to test this change
• Updated TS types
• Updated documentation:
  • https://github.com/software-mansion/react-native-screens/blob/main/guides/GUIDE_FOR_LIBRARY_AUTHORS.md
  • https://github.com/software-mansion/react-native-screens/blob/main/native-stack/README.md
  • https://github.com/software-mansion/react-native-screens/blob/main/src/types.tsx
  • https://github.com/software-mansion/react-native-screens/blob/main/src/native-stack/types.tsx
• Ensured that CI passes