Don't rely on entity bundle fields for views plugins during site installs

Problem/Motivation

During site installs where configuration is split into separate modules, it's possible for a field's base storage field to exist, but not have a bundle assigned to it yet when the view is installed.

This triggers a scenario where the view's dependency is wrongly calculated during installs and doesn't provide the relevant view plugins for the field and its relevant dependencies.

Steps to reproduce

Trigger a site install which installs the following modules:

1. custom_base_module: contains a view with a dependency on a node field "x", as well as the field storage for "x"
2. custom_entity_module: contains a bundle for the node using field "x"
3. custom_entity2_module: contains a second bundle for the node also using field "x"

Proposed resolution

Ignore the bundle checking during site installs.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet