Add container references on adding pagedesigner field

Problem/Motivation

- When adding a pagedesigner field to a content type with existing content, the existing nodes have to be resaved. This should be automated.
- When making a pagedesigner field translatable, existing content translations need to be resaved to add the language specific link to the container. This should be automated.

Steps to reproduce

Adding field:
- Create a node type without pagedesigner field, add some content
- Add the pagedesigner field to the node type
- The container is only created and set on the existing content when you resave the existing nodes.

Translations:
- Enable translations on the node type but not the pagedesigner field
- Add translations to the nodes and add pagedesigner content (pagedesigner takes care of translating the container).
- Then make the field translatable. The existing node translations lose the link to the container and show no pagedesigner content.

Proposed resolution

React to updates/inserts of pagedesigner fields and adjust the entities on the node type (adding the container to the default language and the translations if translatable).

Remaining tasks

- Implement described changes
- Testing

User interface changes

None.

API changes

None.

Data model changes

None.