This fixes x2 problems that have broken e2e tests:

1. Unwanted deprecation notice assertions

Now that #21721 has landed the deprecation notice for useApiFetch within the Navigation Block no longer fires for that block (because it no longer uses the hook!).

Therefore we no longer need to add assertions in our e2e tests to expect the console to warning about this deprecation. This PR removes those assertions from the e2e tests.

and

2. Incorrectly installed dependency of @wordpress/api-fetch

Previously the @wordpress/deprecated dependency was directly installed into @wordpress/api-fetch without using lerna. This has been corrected.

How has this been tested?

On Master branch

• Run e2e test suite.
• You should see failures relating to the useApiFetch deprecation notice above

 Expected mock function to be called with:
    ["useApiFetch is deprecated and will be removed from Gutenberg in version 8.1.0. Please use apiFetch instead."]
    but it was called with:
      174 | 				activeSaveSiteSelector
      175 | 			);
    > 176 | 			expect( console ).toHaveWarnedWith(
          | 			                  ^
      177 | 				'useApiFetch is deprecated and will be removed from Gutenberg in version 8.1.0. Please use apiFetch instead.'
      178 | 			);
      179 | 			expect( enabledButton ).not.toBeNull();

On this PR's branch

• Run e2e test suite.
• You should see no failures relating to the useApiFetch hook

Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• 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.