Move styles into specific waveform styles dropdown area

[jeryj]

What?

Moves waveform style selection from general block styles pane into dedicated Waveform panel

Why?

For long-term, I think waveform selection needs to be a dropdown so we can reserve the Styles pane for traditional combination of styles, not restricted to one waveform setting.

How?

• Add Waveform panel
• Add waveform styles to block json
• Output waveform style options as dropdown

Testing Instructions

• Add a playlist block
• Go to Block Inspector -> Styles
• Choose different Waveform styles from the dropdown

Testing Instructions for Keyboard

Screenshots or screencast

Before	After

Use of AI Tools

[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: jeryj <jeryj@git.wordpress.org>
Co-authored-by: scruffian <scruffian@git.wordpress.org>
Co-authored-by: t-hamano <wildworks@git.wordpress.org>

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

[github-actions]

Size Change: +114 B (0%)

Total Size: 7.68 MB

📦 View Changed

Filename	Size	Change
build/scripts/block-library/index.min.js	333 kB	+114 B (+0.03%)

_{compressed-size-action}

[scruffian]

This makes a lot of sense. We had it like this originally but moved it block styles to try to make the UI more generic. However as you point out this puts us into a corner if we want more layout options for the block in the future.

Let's bring it in.

[t-hamano]

This change will affect all consumers using this slot group, won't it? Why is this reordering necessary?

By the way, for all block-specific settings, we use a panel labeled "Settings".

See: #67813

[jeryj]

This shouldn't have been there. Thanks for catching!

[jeryj]

Reverted in #80111

[t-hamano]

It's not immediately clear what these terms refer to, so I think we need to add a translation context.

[github-actions]

Flaky tests detected in a672209.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/29085218294
📝 Reported issues:

• [Flaky Test] Should navigate inner blocks with arrow keys #39607 in /test/e2e/specs/editor/various/writing-flow.spec.js

[t-hamano]

At the very least, I don't think we should reorder public API slots solely for the purpose of a specific block.

[jeryj]

@t-hamano

I don't think we should reorder public API slots solely for the purpose of a specific block.

I didn't review my AI work closely enough. Trying to move too quickly to get the Podcast Player ready. That was my fault.

[jeryj]

Reverted in #80111