Remove #1847 - the initial fix caused other regressions, and the full fix merits a longer incubation

#1867 Ensure that the qill matches the filter when no time is…

Dedupe, report date backports

We later call Contact.create on both contacts so that should manage the caches for this update 'as well as for any other update'
and solve the bug + reduce locking queries

#1847 Fix datepicker to respect the searchDate offsets

#1865 Remove civiwp and option query strings from redirected …

#1865 Remove civiwp and option query strings from redirected url as they only relate to CiviCRM internal uses

I have some misgivings about this since I suspect the rationale behind the search offsets was primarily about the clunky UI.

Having said that I think the datepicker UI is a bit clunky on this front too as it's not obvious you can choose earlier
dates. This does at least restore established behaviour.

#1847

#1864 Revert changes to ACL test and ACL API class and update…

#1864 - 5.27 backport for search is always including deleted contacts

5.27.1 - Add notes. Update version.

Ensure that when normal routing trackable urls and opens in Joomla go to the frontend not administrator site

Fix function declaration to ensure that passing in frontend variable doesn't cause htmlizing by accident in unit tests

Ensure that when normal routing trackable urls and opens in Joomla go to the frontend not administrator site

Pre-upgrade message for php-intl shows twice

(#1846) Ensure that the `Container` is always fresh when upgrading

Before
------

If you load a new version of the CiviCRM codebase, then a freshness check
should cause the container cache to reset automatically (based on the fact
that various files have new timestamps).

However, it's possible that some kind of bug or omission prevents this from working.
Many developers won't notice such a bug because they're obsessive-compulsive
about clearing caches anyway.

After
-----

If you load a new version of the CiviCRM codebase, then it should use a new
container cache - regardless of how well the freshness check works.

5.27.0 release notes: final edits

#1846 Regression (sorta) Hacks to avoid failure on upgrade due to new field not yet being in the DB

Ensure pricefield value label column is not null on upgrade

#1494 System check for moneyvalueformat: grammar & clarity

translation#48: fix up system check grammar and add pre-upgrade message.