prepare for RNC

[pvinis]

Summary

Renaming everything from react-native-hooks to @react-native-community/hooks.
This is in preparation for a new release under the RNC org.

Test Plan

What's required for testing (prerequisites)?

What are the steps to reproduce (after prerequisites)?

Compatibility

OS	Implemented
iOS	✅❌
Android	✅❌

Checklist

• I have tested this on a device and a simulator
• I added the documentation in README.md
• I mentioned this change in CHANGELOG.md
• I updated the typed files (TS and Flow)
• I added a sample use of the API in the example project (example/App.js)

[pvinis]

I'll wait on this until @dabit3 gives me the OK. I want him to be fully aware of this.

[dabit3]

Looks great @pvinis I appreciate you taking the initiative here and doing the work to make this happen.

[pvinis]

Since you are here, should we skip the release under the current name, and go for a release under RNC with all the latest changes?

[dabit3]

@pvinis I think that makes sense, but I will say do what you think is best based on your judgement.

[pvinis]

I'll merge this, and prepare for a 2.0.0(?) release under RNC.

After that, we can use https://docs.npmjs.com/cli/deprecate to show a message to people that they should install @react-native-community/hooks instead. This can be done for the current package current version, from your account.

(thanks @lucasbento for the deprecation tip!)

[lucasbento]

Awesome 😄

[pvinis]

Thanks both. This is ready. I'll keep it open until we finalize with @Titozzz on the release process, then I'll merge and do a release. Then I'll notify @dabit3 again for a deprecation.

Woop RNC 🙌

[pvinis]

🎉 This PR is included in version 1.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀