More zoomed-in box/violin hover labels fixes

[etpinard]

@plotly/plotly_js This presents a few commits that alters (mostly fixes 😏 ) the box/violin hover behaviour when their corresponding value axis range is within the box/violin q1/q3 values. This PR is essentially generalises #3889

Consider,

Plotly.newPlot(gd, [{
  type: 'box',
  y: [1,2,2,3]
}], {
  yaxis: {range: [1.6, 2.4]},
  hovermode: 'x'
})

Currently on master (ever since #3645, released in v1.45.3), hovering over the box gets us an exception on this line

plotly.js/src/components/fx/hover.js

Line 1187 in 0690162

var p1 = g1[0];

as reported in #3962

---

Commit a4b771c is enough to fix the problem and matches the pre-1.45.3 behaviour:

but notice that min and q3 are shown and q1 and max are not, which looked odd to me.

---

Commit 1634ec8 made q1 and q3 show instead:

which I think is better as we show both "innermost" values, but maybe we could do even better.

---

Commit ce5e5f9 made all box labels show i.e. min, q1, median, q3 and max while avoiding overlaps on the y-axis bounds:

which I feel matches similar scenarios (e.g zoomed-in stack bars codepen) better, but please let me know if you disagree.

[antoinerg]

Thank you for fixing #3962 @etpinard !

As far as I'm concerned, this PR deserves a dancer as it improves things. However, I'll let @nicolaskruchten and/or @alexcjohnson comment on the decision of showing all boxes (ie. ce5e5f9).

[alexcjohnson]

Yep, much better! 💃

Does look a little weird to have the arrows pointing right at the edge of the plot area, but of course this is what we do in other contexts where you're hovering on something off-plot. So maybe at some point we can alter that somehow to make it clearer they're not actually right there. Maybe as simple as getting rid of the arrow altogether, so these ones only have the box?

[etpinard]

Maybe as simple as getting rid of the arrow altogether, so these ones only have the box?

Follow-up in #3985

[etpinard]

Ok, let's start merging things for 1.49.0