Allow the 'entity' property of entity reference fields to be aware of its hierarchy in the typed data tree

Opened a MR with the proposed resolution.

Marking as NR for the architecture of this change. If we get agreement on that, I can follow up with test coverage.

The Needs Review Queue Bot → tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.

Turns out this can be done *a lot* easier by just setting the proper context after the typed data object is instantiated.

The Needs Review Queue Bot → tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.

testbot is having issues

The fix looks really trivial and it's just exposing the information via existing APIs, so I can't really see a downside here.

Thanks @catch, removing Needs architectural review tag as this seems to have gotten a thumbs up to pursue.

Moving to NW for test failures though.

This seems to be causing some kind of recursion or so?

    1)
    Drupal\Tests\field\Kernel\EntityReference\EntityReferenceFormatterTest::testEntityFormatterRecursiveRendering
    PHPUnit\Framework\Exception: Killed
    

@Berdir, yup! And I couldn't figure out a good way to prevent it..

Coming here from 🐛 Paragraph access check using incorrect revision of its parent, leading to issues editing and viewing paragraphs when content moderation is involved. Needs work . Regarding the recursive problem, I am reading this right that the first suggested change did not have any failing tests https://git.drupalcode.org/project/drupal/-/merge_requests/7063/pipeline... as the simplified approach have?