Improve the Views integration for DateRange fields

Follow-up to #2161337: Add a Date Range field type with support for end date

Problem/Motivation

datetime_field_views_data() performs some nice improvements for the Views integration for datetime fields, but has not yet been updated to cover daterange fields, so daterange fields only receive the integration provided by the views_field_default_views_data() fallback. This means that for example, the year-only, month-only, etc. formats aren't available as arguments for daterange fields like they are for datetime fields.

Proposed resolution

Give daterange fields the same Views integration capabilities that datetime fields have.

Remaining tasks

• update path test
• map current 'string' view plugin values/operators to new 'datetime' plugin on the update path using regular_expression operator
• Deciding if we need a stronger message alerting the user to manually review the views being converted (and/or may be a Change record?)

User interface changes

API changes

Data model changes