Deprecated the selectors/actions and components that moved to the block editor module

[youknowriad]

Testing instructions

• Check that if you call, wp.data.select( 'core/editor' ).getSelectedBlock() in the console it works but shows a warning.

• Change an import RichText and use editor instead of block-editor in one of the core blocks and check that there are warnings on the console when used.

[aduth]

This looks like a great way to keep ourselves honest and correct in code 👍

There's still one which needs to be updated. From the failing build:

wp.editor.withColors is deprecated and will be removed. Please use wp.blockEditor.withColors instead.

[youknowriad]

@aduth I think this comes from a plugin :p I wonder if it's time to remove the "plugins" test :)

[aduth]

Alternatively, we may consider another exception in the console trapping to permit warnings (and optionally errors, though probably not to start) from plugins, determined based on ConsoleWarning#location (though, as I write this, the location is probably the deprecated script, not the plugin).

[talldan]

Suggested change

	Autocomplete as RootAutocompete,
	Autocomplete as RootAutocomplete,

[talldan]

Suggested change

	export const Autocomplete = deprecateComponent( 'Autocomplete', RootAutocompete );
	export const Autocomplete = deprecateComponent( 'Autocomplete', RootAutocomplete );

[youknowriad]

What do you all think about removing the plugins tests? cc @gziolo How can we unblock this?

[gziolo]

We can either remove integration with 3rd party plugins or silence this warning on Travis. I would prefer the first one.

[gziolo]

I double checked all deprecated components are still exposed to avoid issues with 3rd party plugins.

I think we should still include an entry in the changelog about all those functions and components which will now warn on JS console so folks using npm package could take same actions.

Otherwise, everything works and looks good.

[youknowriad]

I'm hesitant about the docs as we don't have a formal process for Core deprecations yet. A document is indeed needed but probably not the one we have right now for plugin deprecations and also there's already a bunch of other Core deprecations.

[gziolo]

I was thinking about something like:

in packages/editor/CHANGELOG.md:

### Deprecations

- It's now recommended to use the following components from `@wordpress/block-editor` package:
  - `Component1`
  - `Component2`