make minimum and maximum optional for discovery autobins

[gsfk]

Remove the requirements for minimum and maximum for automatically generated bins in discovery config. Requires bento_lib pr 343

The behaviour is unchanged:

• values in the data that are less than minimum or greater than maximum are ignored (not counted in charts)
• the leftmost bin is everything less than taper_left unless minimum = taper_left
• the rightmost bin is everything greater than taper_right unless maximum = taper right

This matches the behaviour of so-called "manual" bins (where we consider the values for the left-most and right-most bins instead of "taper" values). It also allows for minimum and maximum to be used as meaningful limits in the search UI (rather than, e.g. having awkward hacks such as max age = 125 just so the bins will work)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.59%. Comparing base (38a8c06) to head (ac08d1c).

Additional details and impacted files

@@           Coverage Diff            @@
##           develop     #706   +/-   ##
========================================
  Coverage    95.59%   95.59%           
========================================
  Files          138      138           
  Lines         5805     5805           
  Branches       552      552           
========================================
  Hits          5549     5549           
  Misses         205      205           
  Partials        51       51           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[SanjeevLakhwani]

lgtm

[davidlougheed]

lgtm