Fix GraniteConfig type hints to accept int for multiplier fields

[javierdejesusda]

What does this PR do?

Fixes #44877

Loading ibm-granite/granite-4.0-1b-speech fails with
StrictDataclassFieldValidationError because its config.json stores
embedding_multiplier and logits_scaling as integers (e.g. 12, 8),
but GraniteConfig declares them as float.

The fix updates the type hints for all four multiplier fields to float | int,
matching the pattern already used for attention_dropout in the same class.

• I confirm that this is not a pure code agent PR.
• 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?
• Did you make sure to update the documentation with your changes?
• Did you write any new necessary tests?

[Rocketknight1]

cc @tomaarsen @zucchini-nlp from #44877

[tomaarsen]

This strikes me as a good fix, although I haven't tried it locally. I'm personally a fan of expanding the config type hints a bit with float/int rather than requiring model authors to update their ints to floats.

• Tom Aarsen

[zucchini-nlp]

there are more Granite models with xxx_multiplier, xan you update all of them?

[javierdejesusda]

Updated GraniteMoe and GraniteMoeShared. GraniteMoeHybrid already supports int | float | None.

Let me know if you spot any other fixes or anything else to add!

[github-actions]

[For maintainers] Suggested jobs to run (before merge)

run-slow: granite, granitemoe, granitemoeshared

[zucchini-nlp]

Thanks, I will update other similar fields in separate PR

For context, we decided with Lucain that we don't want to force cast as pydantic does because we want the validation be a lightweight dependency. So instead I will check what other fields could be potentially both and update annotations (already did that for all dropouts)

[HuggingFaceDocBuilderDev]

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.