Fix bug with passing capture_* args to neptune callback
Author: AleksanderWWW
Pull request: yes

# What does this PR do?

<!--
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#create-a-pull-request),
      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:
## What does this PR do

This PR aims to fix a bug that appears when using `NeptuneCallback` with `run=None` and at least one of the `capture_*` params set. 

### Cause of the problem

This is due to the fact, that in one of the methods those params have hardcoded values, but the kwargs passed to the constructor are also passed to that method. Therefore a `TypeError` like this occurs during evaluation:
`TypeError: neptune.metadata_containers.run.Run() got multiple values for keyword argument 'capture_stdout' `

### Solution

Before invoking the problematic method we want to make sure that the `capture_*` params are not present in the callback's state by **temporarily** removing them. Once the method returns, the original kwargs state is restored.


Thanks for opening this PR @AleksanderWWW! Let us know when you want a review 🤗 

Thank you @amyeroberts !

Let me wait for my colleagues at Neptune to share their thoughts on my proposal :smiley: 

Hey @amyeroberts 
It seems that the `integration_utils.py` module has become very long and rather hard to navigate.
It's difficult to find what you're looking for and making changes in more than one place in one PR is a nightmare.
Would it be possible to split it into multiple modules separating different integrations? 

Hi @AleksanderWWW, what kind of structure would you propose for the files?

@amyeroberts 
I thought of something similar to what `pytorch_lightning` has: https://github.com/Lightning-AI/pytorch-lightning/tree/master/src/lightning/pytorch/loggers

The root could be the already existing `integrations` package, but each provider (e.g. Neptune, CometML, etc.) has its own module.
Does it make sense?

---

And btw. the PR is ready for review from the code owners' side :rocket: 

@AleksanderWWW OK, sounds like a good idea. We'd have to make all objects importable from the `integrations` module for backwards compatibility. If you'd like to open a PR I'd be very happy to review :)

> If you'd like to open a PR I'd be very happy to review :)

Will do :)

The failing CI test `ModelUtilsTest.test_use_safetensors` doesn't seem to have anything to do with my changes. Is it possible to maybe rerun it?

@amyeroberts will you merge it once the checks pass? :rocket: 

@AleksanderWWW A fix has been merged into main which should resolve this. Could you try rebasing to include this and trigger an new CI run? 

@amyeroberts Done :smiley: