Query loop block: fix block locking flow for consistency and to prevent breaking out of locking #39908
Description
What problem does this address?
For some of the more advanced blocks, there are what I'll call setup states where you need to take a few steps in order to configure the block in question. Three examples are the navigation block, query loop block, and template part block. Currently, if you lock these blocks during the initial setup stage, different outcomes occur:
Query Loop: doesn't lock
locking.mov
Navigation block: does lock
lock.navigation.mov
Template Part block: does lock
lock.template.mov
This testing was all done with Gutenberg 12.9 and WordPress 5.9.2 using TT2.
What is your proposed solution?
I'm not quite sure what's expected here but I think we need to audit any additional blocks that have this setup state in case someone tries to look early on and have consistency in the outcome. In this case, the outcome could be as simple as updating the behavior of the Query Loop block to be consistent with the other two.
cc @Mamaduka