Option for TaxonomyControl to use apiFetch

[lauravicuna-tech]

If a taxonomy has capabilities set, useSelect won't return the terms due to a rest_forbidden_context error. Could we have an option to pass a prop to toggle between using apiFetch and useSelect in cases where we might need to maintain capability restrictions but still be able to fetch terms?

import apiFetch from '@wordpress/api-fetch';

...
const [ apiData, setApiData ] = useState( null );

/**
 * Get all taxonomies of slug type
*/
useEffect( () => {
	if ( ! useApiFetch ) {
		return;
	}

	apiFetch( { path: `/wp/v2/${ slug }` } ).then( ( posts ) => {
		setApiData( posts );
	} );
}, [ slug, useApiFetch ] );

const selectData = useSelect(
	( select ) => {
		return select( 'core' ).getEntityRecords( 'taxonomy', slug, {
			per_page: -1,
		} );
	},
	[ slug ]
);

const data = useApiFetch ? apiData : selectData;

<TaxonomyControl
	...
	useApiFetch={ true }
/>

[tnke]

Assuming apiFetch is subject to pagination, we might need a way around that. AFAIK "per_page: -1" doesn't work with the REST API, so need to probably just use a large number to start with.

Eventually we should build a pagination for it, but that's a separate task.