ContentModerationRouteSubscriber assumes all parameters in an entity form route contain a 'type' key

Problem/Motivation

In some cases, other systems might use route parameters for storing some metadata about a particular route. One example is layout builder using the following parameter to indicate info about section storage:

'section_storage' => ['layout_builder_tempstore' => TRUE],

Proposed resolution

Content moderation should not throw errors when processing routes that have parameters that do not contain a 'type'.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet