Hide insertion point if a template lock exists.

[jorgefilipecosta]

The insertion point allows inserting a new block by clicking on it, when a template lock exists, insertion should not be possible.

Fixes: #5531

How Has This Been Tested?

Define a CPT with a template lock, verify it is not possible to insert block using the insertion point inserter if a template lock exists.

[aduth]

For the block movers, we assign shouldShowMovers without consideration of isLocked, and this consideration is managed by the BlockMover component itself. Should we do that here? Or at least align the two approaches one way or the other?

[jorgefilipecosta]

Yes, we should be consistent, I updated the code to follow the same logic we now do the check for template locking inside BlockInsertionPointm, like we do for BlockMover.

[janeschindler]

I made a column layout today, locked the template, and still see an inserter point. Perhaps columns can't be locked from the page template?

This is the code I'm using to make the template (part of it). I made a block called 'coltext' that only allows a limited number of options. Ideally the user shouldn't be able to add any blocks, except within the coltext block where they can only add the few I've specifically allowed there.

`
'template_lock' => 'all',
'template' => array(
array('core/paragraph', array('placeholder' => 'Text', 'className' => 'intro') ),
array('neuthalblocks/gmap', array() ),

		array( 'core/columns', array(), array(
			array( 'core/column', array(), array(
				array( 'core/columns', array(), array(
					array( 'core/column', array(), array(
						array( 'neuthalblocks/coltext', array() ),
					) ),
					array( 'core/column', array(), array(
						array( 'neuthalblocks/coltext', array() ),
					) ),
				) )
			) ),
			array( 'core/column', array(), array(
				array( 'core/columns', array(), array(
					array( 'core/column', array(), array(
						array( 'neuthalblocks/coltext', array() ),
					) ),
					array( 'core/column', array(), array(
						array( 'neuthalblocks/coltext', array() ),
					) ),
				) )
			) ),
		) ),

`

[aduth]

@janeschindler This was merged five days ago and hasn't yet landed in a Gutenberg plugin release, so I wouldn't expect you should see any difference yet. Gutenberg 5.6.0 will be released on Wednesday. If you are still having problems after the testing again the latest version, I'd recommend you open a new issue, as it will be the easiest way to track further improvements.