Tools panel: Synced the visible label and accessible name

[im3dabasia]

Fixes: #65241

What?

Updated aria-labels for Tools Panel items to match their visible text.

Why?

Resolved mismatches between visual labels and accessible names, improving accessibility.

How?

Refactored aria-label generation to reflect visible text directly without adding unnecessary text.

Testing Instructions

1. Open the Site Editor > Styles > Colors > Elements options (the ellipsis icon button).
2. Open the Elements options popover.
3. Observe the toggle-able items in the menu have a visible text like H1, H2, etc.
4. Verify that the aria-label matches the visible text for toggle-able items.

Screenshots or screencast

Before	After

[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: im3dabasia <[email protected]>
Co-authored-by: afercia <[email protected]>

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

[im3dabasia]

As mentioned in the issue, there is another accessibility concern: the aria-label is set as "Elements options" while the title of the popover is "Elements"

The required change needs to be made in this file. However, removing the word "options" raises an ESLint error (@wordpress/i18n-no-placeholders-only), which prohibits the use of translation functions with placeholders only.

Code Reference

gutenberg/packages/components/src/tools-panel/tools-panel-header/component.tsx

Lines 177 to 181 in ddfbdcc

	const dropDownMenuLabelText = sprintf(
	// translators: %s: The name of the tool e.g. "Color" or "Typography".
	_x( '%s options', 'Button label to reveal tool panel options' ),
	labelText
	);

I would love to hear your thoughts on how to approach this part of the issue