This PR handles advanced settings on the details block and addresses issues with shortcodes in the 3 core blocks that we modify: cover, media-text, and details.

How to Test: 
1. Add a Details block to a page with some content
2. In the sidebar under the advanced block settings, add a custom HTML anchor, class, and name attribute.
3. Check the front end to ensure all attributes appear correctly in the html.
4. Test the full and wide width settings and ensure they display correctly on the front end.
5. Try placing a shortcode, such as `[icon name="house"]`, inside the details block and ensure it renders on the front end.
6. Test shortcodes on the other two core blocks we modify: media-text and cover.

Theme 3.7.1

fix core block markup modifications

## Description

There are two empty `<p>` tags in the Steps blocks surrounding the description field. This applies to all versions of the Steps block, but just now noticed in Theme 3.7 update.

## How to Reproduce

Steps to reproduce the behavior:

1. Go to any page
2. Add Steps block
3. Add a step and fill in fields
4. Preview and view source

## Screenshots

<img width="563" height="145" alt="Image" src="https://github.com/user-attachments/assets/9a762c71-b055-416c-b0b5-d805b5671bb9" />

<img width="786" height="232" alt="Image" src="https://github.com/user-attachments/assets/d42f4958-4339-4afa-bd16-8c3f377a47c3" />

## Device Information

| Property | Value |
| --- | --- |
| Site URL: | https://dev-ua-orientation.pantheonsite.io |
| Theme: | UA Theme 3.7.0 |
| Parent Theme: | N/A |
| Wordpress Version: | 6.9 |
| PHP Version: | 8.2.30 |
| Multisite? | No |
| Custom CSS? | No |
| Operating system: | Mac OS X 10.15.7 |
| Browser: | Chrome 143.0.0.0 |
| Javascript enabled? | Yes |
| Cookies enabled? | Yes |
| Browser Size: | 1512 x 823 |

### User Agent String

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36

### Plugin List

| Name | Version | Status |
| --- | --- | --- |
| ActiveCampaign Postmark (Official)| 1.19.1 | Inactive |
| Akismet Anti-spam: Spam Protection| 5.6 | Inactive |
| Duo Universal| 1.2.1 | Active |
| LLM Bot Tracker by Hueston| 1.6.0 | Active |
| Pantheon Advanced Page Cache| 2.1.2 | Active |
| Redirection| 5.5.2 | Inactive |
| UA Per-Page Discourage Indexing| 1.0.1 | Active |
| UA Slate Form| 1.1.0 | Active |


If you're using assistive technology, please list those and their version numbers if possible.


An issue related to an accessibility concern

accessibility

Empty <p> tags in Steps block

## Description

When using a details block, the block ID, classes, and name attribute will not appear on the front end. The user is also unable to set the block to wide or full width.

## Expected behavior

The block should behave as any other core block, taking the same props and settings through to the front end

## How to reproduce

Steps to reproduce the behavior. For example:

1. Create a page
2. Add the details block with some dummy content
3. With the details block selected, expand the advanced section of the block settings sidebar
4. Input additional CSS classes, HTML anchor, and name
5. In the block settings toolbar, change the alignment to wide width
6. Save and view the page
7. See that it remains standard width
8. Open the inspect tool to see that the class names, ID, and name attribute have not been set

## Additional information

This is almost certainly the fault of the function we use to modify core block markup. I glanced at the code and it looks like we're rebuilding the details from scratch. We may want to see if there's a way to capture the entire opening details tag from the block itself and use that when we're building our markup.

While we're in there with the markup modifications, another minor bug has come to my attention involving shortcodes on blocks that go through markup modification. Let's add a do_shortcodes call on the block markup before we do any modifications to ensure those are replaced with the proper HTML too.


Details block does not recieve additional props

https://wordpress.org/documentation/wordpress-version/version-6-9/

Anything related to architecture / refactors / project structure

core

research

Research changes in WP 6.9

## Description

Users would like a way to search specifically within the directory system. This could function similar to site search, but only searching entries in the custom post type

## Workarounds

If everyone is on a single page, you could add an in-page search block to the template file. This requires editing theme files and wouldn't be persistent across theme updates

## Mockups / Proposed solution

I think this could probably go above the tag list after the [tag list is redesigned](https://github.com/UA-Stratcom/minerva/issues/621). Prior to the redesign, it could go either in the sidebar above the tag list or in the page header below the h1. @spbrown6 may have a preference or other ideas


Roadmap

Milestones

Theme 3.7.1