Adds missing module_specs for usages of _LazyModule

[jkuball]

What does this PR do?

This PR adds a missing __spec__ to the _LazyModule instances of all models.

When a module is missing a spec it could not be imported via importlib.import_module, which is what torchmetrics does, which is why I've found it in the first place.

Related to #13321 (pr)
Fixes #15212 (issue)

Before submitting

• This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
• Did you read the contributor guideline,
  Pull Request section?
• Was this discussed/approved via a Github issue or the forum? Please add a link
  to it if that's the case.
• Did you make sure to update the documentation with your changes? Here are the
  documentation guidelines, and
  here are tips on formatting docstrings.
• Did you write any new necessary tests?

Who can review?

Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

[HuggingFaceDocBuilder]

The documentation is not available anymore as the PR was closed or merged.

[eroehrig]

😍 exactly what i need

[sgugger]

Thanks for fixing this. Note that it should be added in every _LazyModule but I can take care of that in a separate PR.

[sgugger]

Please use self.assertIsNotNone here.

[jkuball]

Since this is not part of a unittest.TestCase I can't

[sgugger]

It should be in the AutoConfigTest.

[jkuball]

I can and will do that! I just oriented my changes on #13321 which also uses the pure pytest variant.

[sgugger]

Yes, I didn't catch the test was not up to our usual standards in that one :-) Thanks for fixing here!

[jkuball]

I have just moved the test. I also have a local commit lying around that adds the module_spec to all occurences of the LazyModule, but I am not that sure on where to put the tests for that.

Looking at the test_modeling_{{cookiecutter.lowercase_modelname}}.py template I could add the test to both possibilities of the {{cookiecutter.camelcase_modelname}}ModelTester -- but I am not sure on how to import the model beforehand, since I am not that sure on how the Lazy Modules are working exactly.

Can I just add a import transformers.models.{{cookiecutter.lowercase_modelname}} to all model test files, even outside of is_torch_available or would this break things?

[sgugger]

Oh that's great! If you want to include that commit in this PR and rename it that would be great. Regarding tests, I don't think we need more than the test for the auto submodule and the test of transformers (since it's the same thing everywhere). To answer your question however, it does not need to be under a is_torch_available().

To have the PR be perfectly complete, could you also add the change to the modeling template (if you don't have it in your commit already) as well as fix the test for transformers spec to be in a unittest.TestCase?

[jkuball]

Okay, I figured that with the tests, but I wasn't sure.
In theory it wouldn't hurt, but yeah, it's probably okay to test the LazyModule once.

From my side this would now be mergeable, unless I made an error somewhere!

Edit: We could also get rid of the Optional-Hint for the module_spec to prevent those issues from arising later again (or at least the None-default).

[sgugger]

Thank you so much for the wide fix! With the templates properly fixed, I don't think we will get new inits without the module_spec (if someone adds another new submodule, they will copy an existing init), so I think we're good.