refactor(axes): replace integersOnly with maximumFractionDigits

[nickofthyme]

Summary

Adds a way to round axes tick values prior to formatting the numerical values into a string.

⚠️ The Axis.integersOnly prop is now deprecated and replace with maximumFractionDigits ⚠️

Usages

Below shows, toggling maximumFractionDigits between 0 (integers only) and 1 (single decimal or tenths only)

Below shows, toggling maximumFractionDigits between 0 (integers only), 1 (single decimal or tenths only) and 2 (double decimal or hundredths only)

Details

The original logic to add the integersOnly only allowed rounding of the numerical tick value in the case of an integer. This PR expands on that by allowing the chart consumer to set the max number of fractional digits (aka decimals) in a numerical value. This is different than formatting in order to show a value to a max fractional digits, as this can render deceptive ticks and their respective placements, see linked issue.

Drawbacks

This is not an active assignment of ticks given the rounded constraint but rather a passive removal of ticks that do not abide by the constraint. Currently d3-scale does not support asking for ticks in this manner. Thus there are drawbacks to this approach, namely those listed below:

• Nicing end ticks can be removed - Given the range extents, there are some cases where nicing a domain with a restrictive maximumFractionDigits value with result in one or both of the end ticks being removed. See the second gif above as an example of this.
• Tick count is more variable - Say we set maximumFractionDigits to 1 and out data domain is between 0 and 1. Then let's say we desire ~10 ticks, that would be a tick every 0.1 unit. Here we would keep all the ticks as it would maintain all 0.X values. But what if we specify ~4 ticks, d3 would likely give us ticks at every 0.25 unit, in this case all ticks but the 0 and 1 would be removed as then are 0.XX not 0.X. I don't see a way to fix this without iterating a few times, or with custom tick logic.
• Less density of ticks - This is hard to avoid as the very nature of rounding would limit the possible ticks available to show.

Issues

Closes #2220

Checklist

• The proper chart type label has been added (e.g. :xy, :partition)
• The proper feature labels have been added (e.g. :interactions, :axis)
• All related issues have been linked (i.e. closes #123, fixes #123)
• New public API exports have been added to packages/charts/src/index.ts
• Unit tests have been added or updated to match the most common scenarios
• The proper documentation and/or storybook story has been added or updated
• The code has been checked for cross-browser compatibility (Chrome, Firefox, Safari, Edge)
• Visual changes have been tested with light and dark themes

[nickofthyme]

buildkite update screenshots

[markov00]

This doesn't look correct to me, with 0 digit the 1 should not be there, the nice scale shows 0.7 but when changing to 0 fractional digits the 0.7 transforms to 1

[markov00]

Let's merge this and fix the other issue in a subsequent PR, thanks