Fix import form errors

[GilbertCherrie]

This pr removes the constant error messages on the import form

Before:

After:

[miq-bot]

Checked commit GilbertCherrie@6b099c4 with ruby 3.1.5, rubocop 1.56.3, haml-lint 0.62.0, and yamllint
0 files checked, 0 offenses detected
Everything looks fine. 🍰

[Fryguy]

Can we use the chaining operator?

Suggested change

	if (messageData && messageData.level === 'error') {
	if (messageData?.level === 'error') {

[GilbertCherrie]

Not sure, its throwing these errors with it

[Fryguy]

ugh why is Javascript so terrible - ok I guess back to the original code :(

https://stackoverflow.com/questions/59972341/how-to-make-webpack-accept-optional-chaining-without-babel

Looks like it's in webpack 5

[elsamaryv]

I think a good solution is to upgrade webpack and babel packages. However, even with Webpack 4, we can enable optional chaining support by updating the Babel configuration to include the necessary transform plugin, as discussed here

[GilbertCherrie]

@elsamaryv can you review please.

[jrafanie]

this should go back... updated label

[Fryguy]

Backported to spassky in commit 2919572.

commit 2919572963c1d390d597f568a3f030fa09b21454
Author: Jason Frey <[email protected]>
Date:   Mon Aug 18 09:37:05 2025 -0400

    Merge pull request #9498 from GilbertCherrie/fix_import_form_error
    
    Fix import form errors
    
    (cherry picked from commit 94786b7f3945b94b978d214033582fdc21a03cc9)