Add language support to ResourceObject

@bbrala This should be relatively straightforward and would unblock #2794431: [META] Formalize translations support, maybe we can get this going again? :)

Adding plach for original core. Adding gabesullice for review of code both in #2794431: [META] Formalize translations support

Not too sure if this is the time to start testing this. Also, not sure we should go about that.

Appearantly i forgot to change the expected cache tag for the NodeTest. It should now expect the node's language as part of the cache tag :)

Looking very promising! 👍

I've addressed all feedback, only one question left regarding the comment/@see target.

Also i've rebased onto 9.3.x, that was a while back.

Credit @Wim Leers for review.

(note: if you comment on the issue your avatar will become visible here ;))

Was that a random rebase? Seems a bit unneeded perhaps? :)

yes @bbrala, it was a random rebase.

This was split from the parent issue and does not address all issues regarding json:api support for translated content, but it does exactly what the IS says: make the ResourceObject value object language-aware. The existing test (in the context of a node) does not contain any new test coverage for language handling, merely it is extended to include the language ID in the cache keys.

For the narrow purposes for which this ticket is designed, this is RTBC. I only provided reviews on this issue.

Thanks! Adding @bradjones1 to credits :)

Followup created #3252424: Follow-up: ResourceObjectNormalizationCacher should get tags from ResourceObject instead of building them

Committed and pushed f87303bf2d9 to 10.0.x and 797453145e0 to 9.4.x. Thanks!

This is pretty close to a bug but okay let's put this in as a task and roll on :)

+1 for #3252424: Follow-up: ResourceObjectNormalizationCacher should get tags from ResourceObject instead of building them

Thanks @alexpott! I'll put the follow-up in my backlog ;)

WOOOT! 🥳

Does it need a backport to 9.3.x?