Add type annotations for Rembert/Splinter and copies

[jacobdineen]

Splinter and Rembert (Torch) type annotations.
Dependencies on Bert (Torch).
Raw files w/o running make fixup or make fix-copies

#16059
@Rocketknight1

[Rocketknight1]

Hey, I still see a lot of formatting changes in this PR that will probably propagate through the codebase when we make fix-copies! Do you have something like a save hook for PyCharm that always runs black?

[jacobdineen]

ahhh, that could be causing these issues. I have black autoformat on save via vscode, so I'll disable that and put the changes back into these three files

[Rocketknight1]

This looks much better, thank you!

[Rocketknight1]

By the way, GitHub is having some issues right now and tests may not be running. Feel free to continue with the PR, but we'll need to wait for them to come back before we can merge!

[HuggingFaceDocBuilderDev]

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

[Rocketknight1]

Tests are back, going to try fixing copies etc. now, one sec!

[jacobdineen]

Is this a private file? This was the main error I was receiving after run fix-copies (from the build strack trace)

self = <module 'transformers.models.template_bi' from '/home/runner/work/transformers/transformers/src/transformers/models/template_bi/__init__.py'>
module_name = 'modeling_template_bi'

    def _get_module(self, module_name: str):
        try:
            return importlib.import_module("." + module_name, self.__name__)
        except Exception as e:
            raise RuntimeError(
                f"Failed to import {self.__name__}.{module_name} because of the following error (look up to see its traceback):\n{e}"
>           ) from e
E           RuntimeError: Failed to import transformers.models.template_bi.modeling_template_bi because of the following error (look up to see its traceback):
E           name 'Optional' is not defined```

[Rocketknight1]

Ah, I see the problem now! This error is in our template files, and yes, it can be hard to spot, because it only appears when one of our tests tries to generate a new class from the template. Give me a second and I'll see if I can fix it!

[jacobdineen]

I see. Definitely scratched my head at these for a while - Thanks so much for your help!

[Rocketknight1]

Tests are all passing now! Thanks again for your work on this, and your patience as we figured out the templating issues!