State API too large to enable Caching

Problem/Motivation

While investigating (Drupal 10.3) if we should enable the new State_cache see https://metadrop.net/en/articles/what-you-need-know-enabling-state-cache-drupal-103 this module seems to be the largest in our state cache. I see this issue https://www.drupal.org/project/paragraphs_report/issues/3423079 🐛 Why are entities saved in config ? Active recently moved from config to state. But the article I linked to suggests to replace the state API with the key_value one.

Steps to reproduce

On a large site run the sql commands from https://metadrop.net/en/articles/what-you-need-know-enabling-state-cache... and see size of state api.

This module was the biggest offender.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes