gutenberg-mobile PR: wordpress-mobile/gutenberg-mobile#3208

Description

In the native version of the BlockEdit component the context prop is not being passed to the edit component of the block so the context is not available if the usesContext property was set in the block's metadata.

Based on the web version implementation, I added the logic related to fetching and passing the block context to the edit component of a block.

How has this been tested?

We don't have any block that has the usesContext property in the metadata except the core/social-link block. However although this block is registered, it's marked as a hidden block and it's only used as an inner block of core/social-links which already passes its own block context.

Being that said, testing this PR requires to introduce some code changes:

1. Add the following code to a block's metadata (in this example we're going to use the paragraph block):

"usesContext": [ "postId", "postType" ],

2. Add context to the props list in the edit component of the paragraph block.
3. Print the context content by adding console.log( context ); in the component function.
4. Open or create a post and add a paragraph block.
5. Check the app's log and verify that it's printing an object with postId and postType, for regular post it should print {postId: 1, postType: "post"}.

Screenshots

N/A

Types of changes

Bug fix

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• I've tested my changes with keyboard and screen readers.
• My code has proper inline documentation.
• I've included developer documentation if appropriate.
• I've updated all React Native files affected by any refactorings/renamings in this PR.