incorrect name for `torch` extension in PyTorch easyconfigs

[boegel]

a recent enhancement in the run_pip_list function that is used to sanity check the output of pip list:

• enhance run_pip_list function to print warning for mismatched Python package names or versions easybuild-easyblocks#4109

reveals a problem for our PyTorch easyconfigs, for example with --sanity-check-only:

== sanity checking...
  >> loading modules: PyTorch/2.6.0-foss-2024a...
  >> Check on requirements for installed Python packages with 'pip check': OK
  >> Check on installed Python package names and versions with 'pip list': OK

WARNING: The following Python packages were likely specified with a wrong name because they are missing in the 'pip list' output (causes failure if --upload-test-report is set):
pytorch (close matches in 'pip list' output: torch, pooch, pytoml)

Should be easy to fix, just use torch rather than pytorch as extension name, and should be easy to test via --sanity-check-only.

@Flamefire Can you pick up on this?

[smoors]

@Flamefire already looked into this, see
#22357 (comment)

the problem is that we have to convert from PythonPackage easyblock to PythonBundle, but that's stuck because we currently don't allow multiple sources for extensions, see
easybuilders/easybuild-framework#3463

so for now we should just add sanity_check_pip_list = False for PyTorch.

[Flamefire]

the problem is that we have to convert from PythonPackage easyblock to PythonBundle, but that's stuck because we currently don't allow multiple sources for extensions, see easybuilders/easybuild-framework#3463

And I don't like to move to PythonBundle for single packages. Besides the "uglier" syntax (using dicts instead of variables) it "invites" adding new packages instead of using existing ones are adding easyconfigs for them which can be used by others. I had to do some unbundling before already.

so for now we should just add sanity_check_pip_list = False for PyTorch.

Yes. Another idea was to add a parameter like ext_name to Pythonpackage, defaulting to the name of the EC, to a) overwrite the name for the check and b) add that as an extension in the module file so it becomes the same as a bundle with a single extension
But that needs a decision such as if that is considered a "breaking" change or if we really want to push for bundles and deprecated pythonpackage.

I have a bunch of PyTorch PRs open already that add IMKL/ACL and set that.
We could of course just add it to all existing PyTorch ECs in a single PR and merge without testing as there are no other changes.
#26299