Fix move block to position bug; Add test cases;

[jorgefilipecosta]

Description

On #14003 I missed a case where a restriction was still not being applied and the moving blocks were possible when it should not be.

Basically, if an InnerBlocks are contained templateLock insert we should be able to move inside the area but not move an InnerBlock to another root block, that move was still possible.

I also add test cases to the moveBlockToPosition action.

How has this been tested?

Add the blocks available in https://gist.github.com/jorgefilipecosta/c9a9cc1c5199aca6786413492c302ccd.
Add the product block.
Verify none of its nested blocks can be moved outside. (before they could).

[gziolo]

@jorgefilipecosta - can you apply some labels? It looks like a bug, right?

[jorgefilipecosta]

Sorry, I should have applied the labels during the creation but the problem was corrected.

[oandregal]

I've tested this and it works: I couldn't move the inner blocks outside the parent with the fix applied. One thing to note, though, is that the "blue line" indicating a DropZone is still shown.

[oandregal]

For other reviewers: wanted to note that this may be made redundant as per feedback at #14521 (comment)

[jorgefilipecosta]

I've tested this and it works: I couldn't move the inner blocks outside the parent with the fix applied. One thing to note, though, is that the "blue line" indicating a DropZone is still shown.

Hi @nosolosw, the blue line appears in most cases even if the move ends up not being possible (e.g: allowed blocks restrictions, child blocks) so the fact that the blue line appears in this PR is a general problem.

I think we should address the general problem. I think we should expose a selector canMoveBlock... similar to canInsertBlock and in the drop zones components, we can use that selector. I think we can first merge this PR to avoid merge conflicts and then I can apply the refactor.

[draganescu]

I have tested this using the provided instructions and it works as described.