Refactor: Convert class components to functions in element tests

[nextdimension]

What?

Contributes to #22890

Convert class components to function components in element package tests.

Why?

This PR contributes to the ongoing effort to modernize the Gutenberg codebase by converting React class components to function components with hooks, as tracked in #22890.

React's official documentation recommends function components as the modern approach, and this aligns the test code with current React best practices.

How?

• Replace class extends Component with function components
• Update this.props references to use props parameter directly
• Remove unnecessary render() method wrappers

Files changed:

• packages/element/src/test/create-interpolate-element.js
• packages/element/src/test/serialize.js

Testing Instructions

1. Run the element package tests:

   npm run test:unit -- --testPathPattern="packages/element/src/test"
   

2. Verify all tests pass

Testing Instructions for Keyboard

N/A - This PR only affects test files, not user interface components.

Screenshots or screencast

N/A - Test-only changes with no UI impact.

[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.

• Required label: Any label starting with [Type].
• 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.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @chris@ryzhq.com.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Unlinked contributors: chris@ryzhq.com.

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, @nextdimension! 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.