Add geo shape query filter

[VijayanB]

Description

Added Geo Shape Query Filter to build geo shape query for given shape , relations and label.

Issues Resolved

#213

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[codecov-commenter]

Codecov Report

Merging #319 (aacdfd9) into main (e3eef6b) will increase coverage by 0.09%.
The diff coverage is n/a.

📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

@@            Coverage Diff             @@
##             main     #319      +/-   ##
==========================================
+ Coverage   90.26%   90.36%   +0.09%     
==========================================
  Files          12       12              
  Lines         298      301       +3     
  Branches       40       40              
==========================================
+ Hits          269      272       +3     
  Misses         19       19              
  Partials       10       10              

Impacted Files	Coverage Δ
...plugins/dashboards-maps/public/model/geo/filter.ts	100.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[junqiu-lei]

Could we define the type of geo_shape?

[VijayanB]

Geo shape has variable field name property and fixed string property. How do you recommend create type in that case?

[junqiu-lei]

Maybe we can define something like:

type GeoShape = {
  ignore_unmaped: Boolean,
  location: {
    relation: FilterRelations,
    shape: {
      type: 'Polygon',
      coordinates: [
        [
          [number, number],
          [number, number],
          [number, number],
          [number, number],
        ],
      ],
    },
  }
}

[VijayanB]

but location is not fixed. It could be any field name

[junqiu-lei]

In short term I think it's ok to use any, long term we need define the type to make it safer usage

[junqiu-lei]

We might can use generic type for it?

type Coordinate = [number, number];

type Polygon = {
  type: 'Polygon';
  coordinates: Coordinate[][];
};

type Geometry = Polygon;

type Location<F extends string> = {
  [K in F]: {
    relation: 'INTERSECTS';
    shape: Geometry;
  };
};

type GeoShape<F extends string> = {
  ignore_unmaped: true;
} & Location<F> & Geometry;