[PART-4] CPUAggregation Refactor : Add CPU Aggregation support to GridAggregationLayer

[1chandu]

For #3583

NOTE: Splitting #3912 to multiple stacked PRs, will close #3912 (keeping it open for existing discussions to be resolved).

Background

Change List

• GridAggregationLayer:
  • Add support for CPU Aggregation (using same utility methods used for CPUGridLayer).
  • Add required state management to handle various aggregation scenarios (CPU vs GPU, WorldSpace vs ScreenSpace, single vs multiple weight aggregation)
• Update all grid aggregation layers, ContourLayer, ScreenGridLayer, and GPUGridLayer to extend form GridAggregationLayer. [NOTE: CPUGridLayer doesn't use GridAggregationLayer, which requires more sophisticated dimension management, same as `HexagonLayer]
• Add docs and unit tests.

[Pessimistress]

Looks like you are not handling positions64Low for ScreenGridLayer?

[1chandu]

pixelXY64 defined here only to perform fp64 arithmetic for division operation, applies to both world space aggregation and screen space, but I am not actually using low fp64 positions attributes, doesn't seem to be needed, we can add if there is a need.

[Pessimistress]

The projection to clipspace is inaccurate if you don't use the low parts. This applies to both geospatial and non-geospatial.

[Pessimistress]

I'm only making the comment here because GitHub doesn't allow me to comment on a line you didn't change.

[1chandu]

Updated attributes to be 64bit and added attribute to the shader.

[Pessimistress]

• Just use sub layer ids "lines" and "bands". They will be concatenated with the parent layer's id so you don't have to call out that they are children of a contour layer.
• The sub layer ids should be documented in contour-layer.md

[Pessimistress]

This is extremely expensive (creating inline functions inside an iteration).

You should be able to do something like contours[object.contourIndex].color.

Same thing for _onGetSublayerStrokeWidth