Add TFHubertModel
# What does this PR do?
This PR adds the TFHubert Model.
<!--
Congratulations! You've made it this far! You're not quite done yet though.

Once merged, your PR is going to appear in the release notes with the title you set, so make sure it's a great title that fully reflects the extent of your awesome contribution.

Then, please replace this with a description of the change and which issue is fixed (if applicable). Please also include relevant motivation and context. List any dependencies (if any) that are required for this change.

Once you're done, someone will review your PR shortly (see the section "Who can review?" below to tag some potential reviewers). They may suggest changes to make the code even better. If no one reviewed your PR after a week has passed, don't hesitate to post a new comment @-mentioning the same persons---sometimes notifications get lost.
-->

<!-- Remove if not applicable -->

Fixes # (issue)


## Before submitting
- [ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
- [x] Did you read the [contributor guideline](https://github.com/huggingface/transformers/blob/master/CONTRIBUTING.md#start-contributing-pull-requests),
      Pull Request section?
- [ ] Was this discussed/approved via a Github issue or the [forum](https://discuss.huggingface.co/)? Please add a link
      to it if that's the case.
- [x] Did you make sure to update the documentation with your changes? Here are the
      [documentation guidelines](https://github.com/huggingface/transformers/tree/master/docs), and
      [here are tips on formatting docstrings](https://github.com/huggingface/transformers/tree/master/docs#writing-source-documentation).
- [x] Did you write any new necessary tests?


## Who can review?
@patrickvonplaten 
@sgugger 
@Rocketknight1 
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.

<!-- Your PR will be replied to more quickly if you can figure out the right person to tag with @

 If you know how to use git blame, that is the easiest way, otherwise, here is a rough guide of **who to tag**.
 Please tag fewer than 3 people.

Models:

- albert, bert, xlm: @LysandreJik
- blenderbot, bart, marian, pegasus, encoderdecoder,  t5: @patrickvonplaten, @patil-suraj
- longformer, reformer, transfoxl, xlnet: @patrickvonplaten
- fsmt: @stas00
- funnel: @sgugger
- gpt2: @patrickvonplaten, @LysandreJik
- rag: @patrickvonplaten, @lhoestq
- tensorflow: @LysandreJik

Library:

- benchmarks: @patrickvonplaten
- deepspeed: @stas00
- ray/raytune: @richardliaw, @amogkam
- text generation: @patrickvonplaten
- tokenizers: @n1t0, @LysandreJik
- trainer: @sgugger
- pipelines: @LysandreJik

Documentation: @sgugger

HF projects:

- datasets: [different repo](https://github.com/huggingface/datasets)
- rust tokenizers: [different repo](https://github.com/huggingface/tokenizers)

Examples:

- maintained examples (not research project or legacy): @sgugger, @patil-suraj
- research_projects/bert-loses-patience: @JetRunner
- research_projects/distillation: @VictorSanh

 -->

Hey @will-rice,

Wow that was quick! :D Can you remove the [WIP] whenever the PR is ready for review? :-)<|||||>One thing that's different from the PyTorch version is I couldn't use the copy comments because I added the type to the config arguments in Wav2Vec2. If I retained the copy comments it would overwrite HubertConfig with Wav2Vec2Config. Which makes sense, but I wondered if there was a way to fix this so I could keep the copy comments, but ignore the config type.<|||||>I added back the WIP based on the TFWav2Vec2 [bugs](https://github.com/huggingface/transformers/issues/12264#issuecomment-864611327). I will update this with the fixes when those are corrected. <|||||>@patrickvonplaten I believe this one is ready for review now. I updated it with the wav2vec2 bug fixes.<|||||>@patrickvonplaten I can definitely add the copy comments. The issue I ran into was due to Wav2Vec2Config typing in TFWav2Vec2 so the copy script overwrites the TFHubertConfig. I didn't look in depth at the copy code, but I was thinking that we could allow the copy to ignore typing.<|||||>Removing the config typing from TFWav2Vec2 would work though and that's how it is in PyTorch.<|||||>> Removing the config typing from TFWav2Vec2 would work though and that's how it is in PyTorch.

Ah you can add something like `with Wav2Vec2->Hubert` which should correctly replace the class name when copying<|||||>Left a comment here: https://github.com/huggingface/transformers/pull/12206/files?file-filters%5B%5D=.py#r667074787 :-) That's how it should work well with the configs<|||||>> Left a comment here: https://github.com/huggingface/transformers/pull/12206/files?file-filters%5B%5D=.py#r667074787 :-) That's how it should work well with the configs

🤦‍♂️ 

Thanks! I will update it now.