[data.search.aggs] Remove date histogram dependency on timefilter

[lukeelmers]

Part of #65793

Currently aggs (and therefore the search service) has a dependency on the query service which is exclusively due to date_histogram's usage of timefilter.calculateBounds.

timefilter.calculateBounds cannot be moved to the server in its current state because of its use of the optional forceNow parameter, which will look for a forceNow query string parameter on window.location. The forceNow override is used mainly in functional tests, and also a few places in reporting, so it isn't something that we can get rid of entirely without some more extensive work.

In order to make aggs available on the server, we need to ensure date_histogram is no longer reliant on timefilter in its current state.

To that end, this PR makes the following changes:

• Moves the calculateBounds and getTime utilities out of public/query/timefilter and into common/query/timefilter
• Moves the logic used by timefilter.getForceNow into a standalone util in public/query/timefilter/lib
• Removes the query dependency from search service & aggs, and replaces it with a calculateBounds dependency which can be passed in to the date histogram agg type
• The calculateBounds function is defined in public/search/search_service, where it uses the getForceNow util from timefilter to parse the querystring from window.location
• When aggs moves to the server, we will define calculateBounds there without the forceNow option, thus bypassing the need for window

Testing notes
This is a refactor and should introduce no functional changes. Areas to check for possible regressions: date histogram visualizations -- particularly ones where the interval is set to auto -- and reports generated based on such visualizations.

[ppisljar]

code LGTM

[lukeelmers]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 858a9e2

Build metrics

@kbn/optimizer bundle module count

id	value	diff	baseline
data	200	-9	209

History

• 💔 Build #57149 failed 2c5d8691b8ceaec0e880256be9388a95a0d5fff9
• 💚 Build #56107 succeeded 0f0d7e440a885f746264c25573a9c6e92d0b12d2

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream