Fix MiniMax (docs and integration tests checkpoint)

[geetu040]

What does this PR do?

This PR updates MiniMax from #35831 with minor changes

• Checkpoint for integration tests has been changed from geetu040/MiniMax-tiny to hf-internal-testing/MiniMax-tiny as suggested here #35831 (comment)
• Minor Fixes in the docs

Before submitting

• This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).

Who can review?

@LysandreJik, since you merged the original PR, just addressing a couple of items. Thanks and sorry for a late follow-up!

CC: @ArthurZucker, @stevhliu

[stevhliu]

Thanks for the fixes!

[ydshieh]

Hi @geetu040 Could you share the reason we use such tiny checkpoint (with random weights right?) for integration tests? Is it because otherwise we get GPU OOM?

[geetu040]

Hi @geetu040 Could you share the reason we use such tiny checkpoint (with random weights right?) for integration tests? Is it because otherwise we get GPU OOM?

yes @ydshieh, the original model, MiniMax-Text-01, has 456B parameters.

[ydshieh]

run-slow: minimax

[github-actions]

This comment contains run-slow, running the specified jobs:

models: ['models/minimax']
quantizations: [] ...

[ydshieh]

I will merge tomorrow once pytest/custom-tests is green. If it's failing just because the expected values and actual values not matching, I will update.