Add query object support for receive_date_high & receive_date_low and generically date fields

[eileenmcnaughton]

Overview

Further fix on the 5.16 work to switch contribution receive_date over to use datepicker object. We have already merged the main change but it was identified in testing that the low & high date values were not filtering correctly.

Before

Choosing from receive date in advanced search not filtering

After

Choosing from receive date in advanced search filtering

Technical Details

@seamuslee001 I believe in general we should be removing special field handling (when we touch the fields) in favour of generic handling - this accepts the field is 'falling through' to default handling & 'clevers that up' to code with dates

Comments

Todo on here - we should add links to related - @seamuslee001 feel free to help on this bit

[civibot]

(Standard links)

• If this is your first pull-request for CiviCRM, please browse CONTRIBUTING.md for information about the development and testing processes.
• If you are reviewing this pull-request, you may wish to consult the test sites and the Review Standards (long template, short template).

[seamuslee001]

Jenkins is not pleased with your style @eileenmcnaughton https://test.civicrm.org/job/CiviCRM-Core-PR/27230/checkstyleResult/new/

[seamuslee001]

I have tested this and seems to work sensibly from my POV and adds a test adding MOP

[eileenmcnaughton]

@seamuslee001 jenkins is no hipster himself!