IFX bugfix (take 2): avoid Fortran module-file collision

[joewallwork]

Merges into #2875

Fixes IFX CI failure in enzyme/test/Fortran/ReverseMode/allocatableArraySimple_with_explicit_interface.f90 caused by a compiled module-file collision (AD.mod) under parallel test execution.

The test now uses a unique module name and matching use statement so IFX consistently resolves the correct module and avoids error #7005: Error in reading the compiled module file.

[joewallwork]

@copilot How to fix the error #7005: Error in reading the compiled module file. error in the CI for the enzyme/test/Fortran/ReverseMode/allocatableArraySimple_with_explicit_interface.f90 test case under the IFX compiler?

[Copilot]

@copilot How to fix the error #7005: Error in reading the compiled module file. error in the CI for the enzyme/test/Fortran/ReverseMode/allocatableArraySimple_with_explicit_interface.f90 test case...

#7005 here is caused by an IFX module-file collision: multiple tests were compiling module AD in parallel, so this test sometimes read another test’s AD.mod.

I fixed it by giving this test a unique module name and updating the corresponding use line in enzyme/test/Fortran/ReverseMode/allocatableArraySimple_with_explicit_interface.f90 (commit fc99eac).

That isolates the .mod artifact per test and avoids the compiled-module read error.

[joewallwork]

Closing as superseded by #2905.