CiviReport does not handle custom_value_ table prefix from older fields

CiviReport has a hardcoded table prefix check in CRM/Report/Form.php which looks for 'civicrm_value' prefix on tables. In older versions of CiviCRM, these tables were created with a different prefix, 'custom_value'.

If a field in a table created using CiviCRM 1.x is used to restrict a report, then clicking 'Preview' will throw an SQL error as CiviCRM attempts to reference fields which are not included by CRM_Report_Form::customDataFrom(), because it does not recognise those fields as custom data fields.