Content views shipped by node module have non-functional timestamp field

Problem/Motivation

The default shipped views views.view.content and views.view.content_recent both have a timestamp field that is provided by the history module. History module is not a requirement of node module. The field is therefore invalid until history module is enabled. As per our current standing and documentation on configuration dependencies, if a configuration depends on something (in this case history module), it would mean the containing module also needs to depend on it. That is not the case. We also removed content translation fields from these views for similar reasons earlier.

Proposed resolution

Remove the history fields. (Alternately: move the views to standard profile (but at least tests in other modules depend on this view).)

Remaining tasks

Review. Commit.

User interface changes

Users will need to add these fields if/when they enable the history module.

API changes

None.