feat(axes): option to fit domain to list of annotation SpecIds

[nickofthyme]

Summary

Adds the AxisSpec.domain.includeDataFromIds option to YDomainBase. This optional allows specifying a series of SpecIds to include into the domain calculation, respective of their groupId. Currently, only LineAnnotation and RectAnnotation specs are supported, everything else is already included in the domain automatically. Setting domain.max or domain.min will override this functionality.

See pr demo story here

Issues

fix #1411

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

[nickofthyme]

@markov00 I added the rect annotation finite values to the domain. The one question I have is when the domain min is controlled by y0 or the max by y1, the rect annotation covers the full area of the chart with no real indication that it's an annotation without the some type of padding. See example.

I wonder if we should filter the y0 rect annotation values that are below the computed min and y1 values above the computed max.

[markov00]

@markov00 I added the rect annotation finite values to the domain. The one question I have is when the domain min is controlled by y0 or the max by y1, the rect annotation covers the full area of the chart with no real indication that it's an annotation without the some type of padding. See example.

I wonder if we should filter the y0 rect annotation values that are below the computed min and y1 values above the computed max.

I don't see this as a problem. If I'm adding an annotation with a data domain that is bigger then the current chart data domain, and I configured my chart to include the annotation domain into the data once, I don't see this as an issue: a rectangle area that covers entirely the chart works fine for me, it doesn't need anything special

[markov00]

Tested locally, everything works like perfectly, I have also tested with the yNice prop enabled and it follows that correctly.

Please update the PR description with the changes you have done on the naming