Esm checkpointing
Author: Amelie-Schreiber
Pull request: yes

# What does this PR do?

Title: Resolve In-Place Operation Error in ESM Embeddings

Description:

This pull request addresses a critical issue concerning in-place operations within the ESM embeddings module which was causing a `RuntimeError` during the backward pass when training with certain configurations. The error message being encountered was:

```plaintext
RuntimeError: Output 0 of MatMul4BitBackward is a view and is being modified inplace.
```

The modifications in this pull request ensure that in-place operations are replaced with out-of-place operations to comply with the PyTorch autograd's requirement, which disallows in-place operations on tensor views to ensure correct gradient computation. 

Changes:
1. Replaced in-place operations in `modeling_esm.py` with their out-of-place counterparts.
2. Ensured that all tensors being operated upon are not views to avoid the aforementioned `RuntimeError`.

These changes have been tested and verified to resolve the error during the training phase, thus improving the robustness of the ESM module for a wider variety of training configurations.

This resolution is crucial for researchers and practitioners working with ESM models, ensuring smooth training and utilization of the models provided within the Transformers library.

It's important to note that while resolving the in-place operation error is crucial for correct functionality, the switch from in-place to out-of-place operations may have a slight impact on computational efficiency and memory usage. In-place operations are usually more memory-efficient as they don't require additional memory allocation for storing the results; they directly update the values in the original tensors. On the other hand, out-of-place operations create new tensors to store the results, which can increase the memory footprint of the model. 

However, due to the fact that the ESM-2 models are now compatible with QLoRA, this seems negligible and a good compromise. 

<!--
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).
- [ ] Did you read the [contributor guideline](https://github.com/huggingface/transformers/blob/main/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.
- [ ] Did you make sure to update the documentation with your changes? Here are the
      [documentation guidelines](https://github.com/huggingface/transformers/tree/main/docs), and
      [here are tips on formatting docstrings](https://github.com/huggingface/transformers/tree/main/docs#writing-source-documentation).
- [ ] Did you write any new necessary tests?


## Who can review?

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:

- text models: @ArthurZucker and @younesbelkada
- vision models: @amyeroberts
- speech models: @sanchit-gandhi
- graph models: @clefourrier

Library:

- flax: @sanchit-gandhi
- generate: @gante
- pipelines: @Narsil
- tensorflow: @gante and @Rocketknight1
- tokenizers: @ArthurZucker
- trainer: @muellerzr and @pacman100

Integrations:

- deepspeed: HF Trainer/Accelerate: @pacman100
- ray/raytune: @richardliaw, @amogkam
- Big Model Inference: @SunMarc
- quantization (bitsandbytes, autogpt): @SunMarc and @younesbelkada

Documentation: @stevhliu and @MKhalusova

HF projects:

- accelerate: [different repo](https://github.com/huggingface/accelerate)
- datasets: [different repo](https://github.com/huggingface/datasets)
- diffusers: [different repo](https://github.com/huggingface/diffusers)
- rust tokenizers: [different repo](https://github.com/huggingface/tokenizers)

Maintained examples (not research project or legacy):

- Flax: @sanchit-gandhi
- PyTorch: See Models above and tag the person corresponding to the modality of the example.
- TensorFlow: @Rocketknight1

 -->


Comments:
The docs for this PR live [here](https://moon-ci-docs.huggingface.co/docs/transformers/pr_26454). All of your documentation changes will be reflected on that endpoint.