[BUG] ES query rule boundary field changed when editing the rule

[XavierM]

In ES query rule when a boundary field is set up at the creation of the rule. Then, each time that you edit the rule, the boundary field get re-set to another value.

Step to reproduce

1. Create source data and data view:

PUT my-geo-test
{"mappings":{"properties":{"location1":{"type":"geo_point"},"location2":{"type":"geo_shape"}}}}

POST my-geo-test/_doc/
{
  "@timestamp": "2023-08-14T05:00:00.000Z",
  "location1": {
    "type": "Point",
    "coordinates": [
      -71.34,
      41.12
    ]
  },
  "location2": {
    "type": "LineString",
    "coordinates": [
      [
        -77.03653,
        30.897676
      ],
      [
        -77.009051,
        30.889939
      ]
    ]
  },
  "field1": "Wonderland",
  "field2": "The Shire",
  "field3": "Neverland",
  "field4": "Fresno",
  "other1": true,
  "other2": "abc123"
}

POST kbn:/api/saved_objects/index-pattern/my-geo-test*
{"attributes":{"fieldAttrs":"{}","title":"my-geo-test*","timeFieldName":"@timestamp","sourceFilters":"[]","fields":"[]","fieldFormatMap":"{}","typeMeta":"{}","runtimeFieldMap":"{}","name":"my-geo-test*"}}

2. Create a tracking containment rule in the UI and select field4 as the human readable boundary field

3. Edit the rule and observe the Boundary field selection changes to field1

The field change does not take effect unless you actually click SAVE, but this can result in accidental misconfigurations.

Originally posted by @rseldner in https://github.com/elastic/sdh-kibana/issues/4012#issuecomment-1678260324

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[guskovaue]

Agreed that gis team continue with refactoring, since they have bigger knowledge of the code and issues with it.

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)

[nreese]

Problem is larger than just BoundaryIndexExpression. EntityIndexExpression also does the same thing and resets entity geo field and entity date field on page load.