Ansible request for GCC 7.5.0 on Fedora 40

Delete as appropriate from this list:

- Bug in ansible playbook

Details:
It's possibly that our self-built GCC 7.5.0 is not working correctly on recent distributions of Fedora. Attempting to build OpenJ9 JDK11 as part of VPC seemed to fail with a compiler issue during the configure step.
We should check what the underlying error is and if appropriate remove the GCC 7.5.0 from the installation on appropriate Fedora versions in order to avoid confusion:
https://ci.adoptium.net/view/Tooling/job/VagrantPlaybookCheck/2083/OS=Fedora40,label=vagrant/console
```
configure: Using default toolchain gcc (GNU Compiler Collection)
configure: Will use user supplied compiler CC=/usr/local/gcc/bin/gcc-7.5
checking resolved symbolic links for CC... no symlink
configure: Using gcc C compiler version 7.5.0 [gcc-7.5 (GCC) 7.5.0]
checking whether the C compiler works... no
configure: error: in `/home/vagrant/openjdk-build/workspace/build/src':
configure: error: C compiler cannot create executables
See `config.log' for more details
configure exiting with result code 77
Error: No configurations found for /home/vagrant/openjdk-build/workspace/build/src.
Please run 'bash configure' to create a configuration.
```

Start with the VagrantPlaybookCheck 2083 console output for Fedora 40 and inspect the OpenJ9 configure failure, especially the referenced config.log. Trace where the Ansible playbook installs or selects GCC 7.5.0 for Fedora, then determine whether the compiler should be removed on affected versions. Done means the underlying failure is understood and the playbook behavior is corrected or documented.

Written by the indexing model from the issue text.