Fix: Use break-word instead of break-all in attribute description

[himanshupathak95]

Fixes: #66998

What?

Changed CSS word-break property from break-all to break-word in meta fields for better text readability when content wraps.

Why?

Currently, text in meta fields breaks incorrectly within words (e.g., "white" breaks as "whit e") due to using break-all. This creates poor readability, especially for descriptions and long text content. Using break-word ensures text breaks at appropriate word boundaries.

Testing Instructions

1. Add this test code to create a custom post type with meta fields in functions.php in your theme:

function init_test_meta_fields() {
   register_post_type(
       'landmark',
       array(
           'label'        => 'Landmark',
           'public'       => true,
           'supports'     => array( 'title', 'editor', 'comments', 'revisions', 'trackbacks', 'author', 'excerpt', 'page-attributes', 'thumbnail', 'custom-fields', 'post-formats' ),
           'has_archive'  => true,
           'show_in_rest' => true,
       ),
   );
   register_meta(
       'post',
       'landmark_description',
       array(
           'object_subtype' => 'landmark',
           'label'          => 'Description',
           'show_in_rest'   => true,
           'single'         => true,
           'type'           => 'string',
           'default'        => 'Inspired by the Eiffel Tower, this red and white tower is one of Tokyo\'s most recognizable landmarks.',
       )
   );
}

add_action( 'init', 'init_test_meta_fields' );

2. Create a new Landmark post
3. Check the attributes >> content desctiption field in meta fields
4. Verify text now breaks correctly at word boundaries
5. Test with various content lengths including URLs and long words

Screenshots

Before word-break: break-all; :

After word-break: break-word; :

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

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

[github-actions]

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @himanshupathak95! In case you missed it, we'd love to have you join us in our Slack community.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.