Problem/Motivation
When requesting a list of entities with an included relation where only the 'view label' operation is allowed, you'll could get an error saying that you try to use a route that does not exists if the public field name is different then the internal field name. This happens because the route name is generated using the internal field name instead of the public field name.
Proposed resolution
Make sure the EntityAccessDeniedHttpException is created with the public field name as $relationship_field parameter instead of the internal field name.
Remaining tasks
None? Maybe add some tests.
User interface changes
None.
API changes
None.
Data model changes
None.