feat(planning): adds physical and logical nodes for range aggregation

[ashwanthgoli]

What this PR does / why we need it:

Adds physical and logical plan nodes for range aggregation. We could have each aggregation operation represented as a different node but this feels like a good starting point.

Physical plan is also called RangeAggregation, it does not say how the aggregation is being performed. This will be updated in a follow-up once we have a basic version of the execution operator.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Checklist

• Reviewed the CONTRIBUTING.md guide (required)
• Documentation added
• Tests updated
• Title matches the required conventional commits format, see here
  • Note that Promtail is considered to be feature complete, and future development for logs collection will be in Grafana Alloy. As such, feat PRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.
• Changes that require user attention or interaction to upgrade are documented in docs/sources/setup/upgrade/_index.md
• If the change is deprecating or removing a configuration option, update the deprecated-config.yaml and deleted-config.yaml files respectively in the tools/deprecated-config-checker directory. Example PR

[owen-d]

Nits, then LGTM.

[owen-d]

Nit: I wouldn't refer to this as partitioning, as that insinuates we're grouping by values:

• Partitioning creates logical or physical boundaries in your data based on column values
• Ordering arranges rows in a specific sequence
• Projection filters which columns appear in results

Instead I'd call this soemthing like Columns, Projection, or ProjectedColumns.

[ashwanthgoli]

Partitioning creates logical or physical boundaries in your data based on column values

^ this is what i was intending it to be

• Range aggregation would partition the data using the column values
• For each partition, it runs the aggregation over the time window
  • Aggregation is run for each step if its a range query

I am of the idea that we would implicitly only project the partition columns (or all stream columns if partitioning is not defined), but we can make this explicit