[Lens] fix error for minInterval>computedInterval for XYChart

[mbondyra]

Summary

Fixes throwing an error for minInterval>computedInterval for XYChart - when user chooses timerange with Daylight Saving Time in between, the minInterval causes throwing an error in elastic-charts library. Fix: We don't need to pass minInterval to any other case except for single bar chart (that was the reason the bug was introduced here: (#61452) so I've just limited the case. Confirmed with @markov00 .

In addition, when testing, I checked the following scenarios for multiple layers:

1. Chart of two layers, one layer with many values, second layer with 0
2. Chart of two layers, many to 1(value)
3. Chart of two layers, many to many
4. Chart of two layers, 1 to 1(different timestamp)
5. Chart of two layers, 1 to 0
6. Chart of two duplicated layers

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• This was checked for keyboard-only and screenreader accessibility
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser
• This was checked for cross-browser compatibility, including a check against IE11

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[elasticmachine]

Pinging @elastic/kibana-app (Team:KibanaApp)

[wylieconlon]

@mbondyra I'm trying to test this PR with an example that is definitely broken: what steps have you been using that are known to be broken?

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 380cfba

History

• 💚 Build #37529 succeeded 380cfba
• 💚 Build #37491 succeeded 766d07f
• 💚 Build #37424 succeeded 466bab3

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

[mbondyra]

@wylieconlon if you create a date histogram, including the date range consisting Daylight Saving Time, it will break for sure (eg.from Mar 17, 2020 @ 10:14:50.570 to Apr 1, 2020 @ 10:15:09.856). Here's the example screenshot:

[timroes]

Hint for that: It must include a DST switch in the timezone you're using :-) So I think the above given time range would include one for European time zones, but not for most US time zones.

[timroes]

Tested on Chrome Linux. Tested one layer with DST switch in it, and tested multiple layers where one layer has only one bar and the other multiple.

Both failed before that, and work with the fix. Code LGTM

Also a hint: you can test the second scenario, by editing the DSL of a filter directly to match something like:

{
  "query": {
    "bool": {
      "should": [
        {
          "match_phrase": {
            "FlightNum": "00PKULZ"
          }
        },
        {
          "match": {
            "_index": "kibana_sample_data_logs"
          }
        }
      ]
    }
  }
}

Where one part of the filter will only match ONE document in that one index and the other just on the index name of the 2nd layer.