feat: use keyboardAppearance instead of global appearance

[kirillzyusko]

📜 Description

Removed default as a possible value of appearance property.

💡 Motivation and Context

The thing is that for default a real keyboard appearance can be dark or light depending on device preferences. In this PR I decided to combine the logic on a native side and simplify JS logic, so for that I removed default as a possible value from a native side.

The other improvement is that we can consume appearance property from useKeyboardState. For that I had a separate listener to KeyboardEvents (keyboardWillShow event), because we need to know the actual field value before keyboard appears.

I removed a code that was responsible for detecting keyboard color from KeyboardToolbar - now we can just use const appearance = useKeyboardState(state => state.appearance) and don't go to low level stuff with setting up listeners. Just pass selector 😎

📢 Changelog

JS

• change appearance in useKeyboardState hook on willShow event;
• use useKeyboardState instead of useColorScheme;

iOS

• remove default as possible value for appearance;

Android

• remove default as possible value for appearance;

🤔 How Has This Been Tested?

Tested manually in example app.

📸 Screenshots (if appropriate):

images taken when you set keyboardAppearance="dark"

Before	After

📝 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
207795 bytes	207793 bytes	2 bytes 📈