fix: lora dropout applied to all models

[Optimox]

Context

What is the purpose of this PR? Is it to

• add a new feature
• fix a bug
• update tests and/or documentation
• other (please add here)

Related to issue #996

Changelog

I only pass the lora_dropout argument where needed

Test plan

Please make sure to do each of the following if applicable to your PR. (If you're not sure about any one of these just ask and we will happily help.)

• run pre-commit hooks and linters (make sure you've first installed via pre-commit install)
• add unit tests for any new functionality
• update docstrings for any new or updated methods or classes
• run unit tests via pytest tests
• run recipe tests via pytest tests -m integration_test
• manually run any new or modified recipes with sufficient proof of correctness
  • include relevant commands and any other artifacts in this summary (pastes of loss curves, eval results, etc.)

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/torchtune/995

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 408dbb5 with merge base f35e5d6 ():
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[ebsmothers]

Thanks @Optimox for finding this bug and making the fix! Can you also update the Mistral components while you're at it?

[Optimox]

@ebsmothers yes you are right I forgot to update the mistral model! I've just added a new commit to take care of it!

[ebsmothers]

Ah sorry just a couple more output layers.. here, here, and here. After that I think this should be good to go!

[Optimox]

@ebsmothers good catch! updated!

[ebsmothers]

Looks good! Thanks again for catching and fixing this. Just kicked off CI, once it's green I can merge.