Required fields should stay required

Problem/Motivation

If a field is required, setting it to use the Read Only form widget should not un-require it.

Steps to reproduce

Configure a field to be required in the field settings, no default value. Go to form display and set that field to use the Read only widget. Create content with no value passed in (so no entity reference prepopulate for example). It will save without validation error preventing this.

Proposed resolution

Probably some people are relying on the current behavior. Could it be made configurable on the widget?

Remaining tasks

User interface changes

API changes

Data model changes