Problem/Motivation
views.view.content.yml uses 'field' as the plugin for the language field, yet 'field_language' plugin exists for this purpose
(and is used because of overrides in views_data anyways). The config should match the result rather than relying on an
override here (ie, the config should match that field_language plugin is used.
The schema should be updated to match.
This was revealed as a symptom of the problem being addressed in #3458099: Views handler loading should respect configuration and was suggested by @catch to tackle in a separate issue.
Steps to reproduce
This was revealed as a symptom of the problem being addressed in #3458099: Views handler loading should respect configuration, if the views handler manager respects the configuration, then this view configuration would have issues.
Proposed resolution
Sort out the configuration and schema
Remaining tasks
Merge request review
User interface changes
None
API changes
None
Data model changes
None
Release notes snippet
The default view configuration for the Admin > Content view now uses the correct Language field plugin.