Query Loop polishing issues for 6.7

[ntsekouras]

This is a non exhaustive list of issues we could aim to land for 6.7 to improve the user experience around this block.

More issues will be added and please feel free to add or suggest more to be included.

• Query Loop deletion from template: make the warning message more understandable by adding context #63350
• Feedback on Query Loop Block settings language #31158
• Context detection for Query block #30369
• Query loop: Clarify the Max page to show setting #63028
• Query Loop Block: Continued iteration on bundled patterns #49280 particularly for a blog pattern
• Replace “post type” with “content type” and the dropdown should be radio if there are only two options.
• Query loop - remove current post ID for ‘related posts’ #42810
• Use "Design" panel for Query Loop block #63497
• 'Inherit query from template' setting is confusing #63598
• 'Force page reload' setting is confusing #63599
• Query in front-page template should respect homepage settings #42554

[jeryj]

Do we want to set the default value of the query block to be inherit as well? If so, here's a quick PR for it: #63362

[ktmn]

Query Loop deletion from template: make the warning message more understandable by adding context

This message has never done anything but needlessly interrupt me, unfortunately.

Perhaps this kind of hand-holding stuff could be grouped and opt-out-able when you first onboard. Some people will make hundreds of sites but on every new site the editor will assume you know nothing.

[Marc-pi]

IMHO the most needed improvement is the skip current post ID
#42810

[brnhrst]

Nice to see some progress on this block. How about adding more options for the sort order, like #51290 or #50999? In my opinion, these are low-hanging fruit that would greatly improve this block for the end user.