Fix: extra wp-block-navigation getting on ul tag

[up1512001]

What?

• created function similar to get_block_wrapper_attributes which support extra parameter to exclude some class.

Why?

Fixes #62690

How?

• as get_block_wrapper_attributes enters default block class, which causes issues by having the block class on the inner container if it's used.

Testing Instructions

• create navigation menu
• check ul tag
• now there will not be wp-block-navigation class which should only be present on main navigation wrapper

Screenshots or screencast

[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: up1512001 <up1512001@git.wordpress.org>
Co-authored-by: talldan <talldanwp@git.wordpress.org>
Co-authored-by: scruffian <scruffian@git.wordpress.org>

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

[up1512001]

@talldan can you please review this PR?

[talldan]

@up1512001 I'm not really sure I know the PHP code for the navigation block well enough or how the block is supposed to function in terms of that wrapper. I've added a few other reviewers who may be able to help.

My instinct is that such a close copy of get_block_wrapper_attributes wouldn't be needed, but perhaps a simplified one that handles merging the classes and styles and outputting them in a similar format.

[scruffian]

I wonder if a simple regex is better? #63801