Refactor: URLInput component to functional react component

[yashjawale]

What?

See #22890

This PR refactors URLInput component from class based component syntax to newer functional component syntax.

Why?

Class based components are no longer the recommended approach & instead functional syntax with hooks is more recommended
The code becomes more readable & easier to make changes to

How?

• React hooks are used for component lifecycle methods
• The withSelect Higher-Order Component (HOC) is replaced by the useSelect hook from @wordpress/data
• Rest of component logic remains the same
• Existing comments are preserved

Testing Instructions

• To test this component try converting any text to link, the URL input box uses this component
• The suggestions are also provided by the same component
• The component should behave same as before

Screenshots or screencast

I'm new to gutenberg contributions, feel free to provide suggestions for improvement & pointing out mistakes
Thanks!

[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: yashjawale <[email protected]>

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

[yashjawale]

CI issues have been resolved for this PR & it is ready for review