Remove legacy babel plugins

[joshualip-plaudit]

What?

Closes #74915

This just removes the forced inclusion of the old plugins.

Why?

Babel has been able to automatically manage whether the transforms that the forcibly-included plugins apply for a while now. Removing them from the forced-includes list just allows code built with WordPress's Babel config to use some "new" operators.

How?

I removed the forced inclusions.

Testing Instructions

Build a file that uses the ??= operator with WordPress's babel config. If it comes out un-transformed, then the issue has been resolved.

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

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: joshualip-plaudit <joshualipstone@git.wordpress.org>
Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>

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

[Mamaduka]

Pinging a couple of folks who are more familiar with this package - @aduth, @jsnajdr, @youknowriad