Avoid `text_config_dict` and `vision_config_dict` being saved  for CLIP-like models
# What does this PR do?

**Avoid `text_config_dict` and `vision_config_dict` being saved  for CLIP-like models.** So less confusion.

Currently, configuration classes for CLIP-like models will save both `text_config` and `text_config_dict`, if `text_config_dict` is provided (as `kwargs`). Similarly, for  `vision_config` and `vision_config_dict`. Many configuration files on the Hub have all these keys, and they look really confusing, see for example [openai/clip-vit-base-patch16](https://huggingface.co/openai/clip-vit-base-patch16/blob/main/config.json) or [laion/CLIP-ViT-H-14-laion2B-s32B-b79K](https://huggingface.co/laion/CLIP-ViT-H-14-laion2B-s32B-b79K/blob/main/config.json#L115)

This issue dates back before the PR #19954. The PR #19954 tried to avoid the usage of `text_config_dict` and `vision_config_dict` (while keeping back compatibility), it didn't prevent `text_config_dict` and `vision_config_dict` being saved.

This PR:
  -  avoid `text_config_dict` and `vision_config_dict` being saved,
  - make sure all the values provided in `text_config_dict` and `vision_config_dict` will be used to update `text_config` and `vision_config` (so backward compatibility), and only `text_config` and `vision_config` are saved
  - **therefore, we can load a existing configuration, save it and upload it again --> make it clean + less confusing, and not break anything**

 I will apply the same change to other CLIP-like models if the idea/approach is accepted.
> Thanks! This may need to be copied over some CLIP-like models that also have some backward-compatibility code with the config dicts.

Sure, in the plan already. Quoted in the PR description

> I will apply the same change to other CLIP-like models if the idea/approach is accepted.<|||||>_The documentation is not available anymore as the PR was closed or merged._