Added CSS which truncates long texts inside suggestions list

[n2erjo00]

What?

This PR removes horizontal scrolling from link suggestion list which appears when adding link to Image block.

Why?

Closes #58497

Horizontal scrolling creates accessibility concerns.
It is also nice that feel and function between different suggestions lists are same

How?

With the power of CSS.

Testing Instructions

1. Open a post or page.
2. Insert a Image block.
3. Add link to that Image block. Navigate the list of suggestion using keyboards

It should be noted that you need have page(s) or post(s) with really long titles to see any

Testing Instructions for Keyboard

Screenshots or screencast

Before

After

[github-actions]

Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Type-related labels to choose from: [Type] Automated Testing, [Type] Breaking Change, [Type] Bug, [Type] Build Tooling, [Type] Code Quality, [Type] Copy, [Type] Developer Documentation, [Type] Enhancement, [Type] Experimental, [Type] Feature, [Type] New API, [Type] Task, [Type] Technical Prototype, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core.
• Labels found: .

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

[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: n2erjo00 <n2erjo00@git.wordpress.org>
Co-authored-by: afercia <afercia@git.wordpress.org>

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