Configuration should not be stored in states.

I noticed that cloudinary_sdk configuration became a state.
Regarding to the Drupal documentation, here is a risk to loose these settings.

State information differs from configuration in the following ways:

It is specific to an individual environment.
You will never want to deploy it between environments.
All state information is lost when you reset the database (i.e. re-install the site from config or drop the database). By contrast, exported configuration can remain in the codebase and will be re-imported upon site installation.