Use the Query title block to display a "Blog" title on any template

[snehapatil2001]

What?

This PR introduces a new variation to the Query Title block, enabling it to automatically display a "Blog" title on relevant templates (e.g., index and home templates) when the archive title is not available. This aims to eliminate the need for manually adding a heading block above the query loop on these templates.

Why?

The issue was that on certain templates (like index and home), the archive title did not show anything by default. This required site creators and theme developers to manually add a heading block, which felt redundant. By adding this functionality to the Query Title block, we simplify the process and ensure that a default "Blog" title is automatically displayed when applicable.

Reference: Issue #64567

How?

• A new "blog title" variation is added to the Query Title block.
• The block automatically detects if it is being used on templates like index or home and displays the "Blog" title when no other archive title is available.
• This ensures the block works out of the box on these templates without additional configuration.

Testing Instructions

1. Open a template that uses the Query Title block, such as an archive, index, or home template.
2. On the index or home templates, verify that the block now displays a "Blog" title automatically.
3. On archive or search result templates, verify that the block displays the appropriate archive title (e.g., category name, search term).
4. Verify that you no longer need to manually add a heading block above the query loop on the index or home templates.

Testing Instructions for Keyboard

1. Navigate to the Query Title block using keyboard controls.
2. Ensure that the title is properly focused and can be edited as expected.
3. Confirm that the block works correctly when using keyboard navigation on index and home templates (displays "Blog") and on archive templates (displays the correct archive title).

[github-actions]

Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Type-related labels to choose from: [Type] Automated Testing, [Type] Breaking Change, [Type] Bug, [Type] Build Tooling, [Type] Code Quality, [Type] Copy, [Type] Developer Documentation, [Type] Enhancement, [Type] Experimental, [Type] Feature, [Type] New API, [Type] Task, [Type] Technical Prototype, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core.
• Labels found: .

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: snehapatil2001 <snehapatil02@git.wordpress.org>
Co-authored-by: codewizard13 <codeslayer2010@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[codewizard13]

Hi @snehapatil2001! Appreciate your work on this so far - this is a badly needed feature. However, it appears the merge is blocked - Can you fix the issue so this can get properly merged?

[snehapatil2001]

@codewizard13 Fixed the issue. 👍