Opt into static_cache for component config entities

🤔 This seems fine, because it's just PHP memory consumption that would grow, not APCu.

I'd prefer to do this first, and to then re-assess whether ✨ PageRegion::loadForTheme can statically regions cache per-theme Active is still relevant.

This looks good to me, but I'd love to have @larowlan confirm that he also sees no reason to NOT do this.

I don't have any objections to this

Great — this now just needs updates to 3 tests, which apparently rely on the fact that there has not been static caching so far.

@mglaman: that screenshot in the issue summary, which route is that for, and for how big of a component tree is it?

Related: 📌 Implement `lookup_keys` in Component for optimized queries Active — this issue is for making (repeated) loading of a specific Component (with known ID) faster. #3528847 is about making querying them faster.

@mglaman: that screenshot in the issue summary, which route is that for, and for how big of a component tree is it?

It was the GET on experience_builder.api.layout.get. The tree wasn't huge, maybe 12 components with various nested slots.