Date API Date argument set-up form changed

The set-up of the date_api_argument_handler in the Date API changed as of version 6.2.2 of the Date APi. This patch to civicrm.views.inc allows for that change and adapts the view integration modules of CiviCRM to that change.

Without this patch the Date APi 6.2.2+ prevents you from choosing between the different fields in the civicrm_event table to use as the argument for the calendar. Though the default view's set-up still works, which uses civicrm_event.start_date by default. This patch once again allows you to choose between the four date fields in civicrm_event( Start Date, End Date, Registration Start Date & Registration End Date) while using the newest versions of the Date API 6.2.2+

This also means that the Dat APi integration has the following requirements
CivicRM < 2.2.3 has no integration with Date API
CiviCRM 2.2.3 -2.2.7 uses the code in Date API 6.2.1 with the patch, outlined here http://drupal.org/node/453688.
CiviCRM 2.2.8+ uses Date APi 6.2.2 with the patch this patch to Date API, outlined here http://drupal.org/node/453688

CiviCRM 2.2.3 + will not require the Date API patch once Date API 6.2.3 is released, though this patch will still be needed to use Date API 2.2.2+