migrate: use the strict=false option, to avoid a BOA 2.3 bug when migrating sites (this should probably use a Provision service).

provision_civicrm.inc: function _provision_civicrm_is_site_context(): remove the  argument, which isn't used anymore.

Issue #2364871: issues with BOA 2.3 not loading the civicrm.drush.inc file if it's located in the install profile (added for verify/clone/migrate and a bit of cleanup).

Issue #2364871: issues with BOA 2.3 not loading the civicrm.drush.inc file if it's located in the install profile.

_provision_civicrm_upgradedb: show the upgrade output as a warning. Most civicrm upgrades show instructions that the user should read.

Update and fixurls: use functions from civicrm.drush.inc instead of duplicating the code (now possible since we use the version-specific civicrm.drush.inc from civicrm.)

Issue #1097554: README.txt: removing from TODO about civimail/membership crons, since now handled by hosting_civicrm_cron.

refs #2133493: remove civicrm.drush.inc to avoid 'Cannot redeclare civicrm_drush_command()' error in Aegir 2.x + avoid duplication/fork of civicrm.drush.inc.

v2/install.provision.inc: cleanup old checks for versions, since we have already checked at this point in the run.

In a migrate operation, the civicrm_version option is mysteriously not available. Until we fix that bug, better to assume we are running civicrm >= 4.2.

Lots of cruft remains for older versions of CiviCRM. In order to
continue supporting these, we are duplicating our code across v1 and v2
directories. v1 will remain untouched from this point forward, and thus
continue to support older CiviCRMs. v2 will be refactored to better use
Aegir2's coding style, work with the hosting_civicrm front-end module,
and thus allow significant code clean-up.

We are switching which code-base to include based on an option that
will be set by the front-end module. If this variable is unset, or less
than 4.2, the older code will be used.