Description

A frequent thing I'm hearing regarding the Serializer is that the diagram in the docs is the most used piece of doc by many developers, as they always forget which direction is normalization, and which is denormalization.

In the new JsonEncoder component, I see we are reusing this name. I think it would be good if we can maybe try finding a different name for this.

On top of the general confusion about the name, it's also a slightly different concept in both components. I think using the same name in 2 components in the same scope can reduce DX as well. For instance, it will probably not be immediately clear what normalizer we talk about in doc articles like How to Create your Custom Normalizer (given we're probably going to document JsonEncoder somewhere in the "Serializer" guides as well). It can also lead to IDE autocompletion suggesting the wrong interface (like what we're discussing for a different class conflict in #58991).

Can we think of a different name for the classes? (e.g. ValueTransformer) And maybe clearly document the direction in the method name (something like encodedValueToPhpValue()?).

cc @mtarld @chalasr