add support for feature-collection indexing

Data Definition team has harmonized the geo-shape payload on bulk-records. Any records that has geo-shape, must be GeoJson and must conform to the schema mentioned here. All shapes must be put in FeatureCollection.

Earlier implementation of indexer service was missing this key shape hence geo-shape indexing and search workflows was broken.

This MR adds support for FeatureCollection indexing. It also adds official opendes:wks:master-data--Wellbore:1.0.0 as integration test to validate index and search workflow.

This MR also fixes few schema parsing errors which we discovered while enabling opendes:wks:master-data--Wellbore:1.0.0 indexing.

testing/indexer-test-azure/src/test/java/org/opengroup/osdu/step_definitions/index/record/Steps.java

@@ -14,14 +14,13 @@
 
 package org.opengroup.osdu.step_definitions.index.record;
 
+import cucumber.api.DataTable;
 import cucumber.api.Scenario;
 import cucumber.api.java.Before;
-import lombok.extern.java.Log;
-
-import cucumber.api.DataTable;
 import cucumber.api.java.en.Given;
 import cucumber.api.java.en.Then;
 import cucumber.api.java.en.When;
+import lombok.extern.java.Log;
 import org.opengroup.osdu.common.SchemaServiceRecordSteps;
 import org.opengroup.osdu.util.AzureHTTPClient;
 import org.opengroup.osdu.util.ElasticUtils;
@@ -69,8 +68,8 @@ public class Steps extends SchemaServiceRecordSteps {
         super.iShouldBeAbleToSearchRecordByTagKeyAndTagValue(index, tagKey, tagValue, expectedNumber);
     }
 
-    @Then("^I should be able search (\\d+) documents for the \"([^\"]*)\" by bounding box query with points \\((-?\\d+), (-?\\d+)\\) and  \\((-?\\d+), (-?\\d+)\\) on field \"(.*?)\"$")
-    public void i_should_get_the_documents_for_the_in_the_Elastic_Search_by_geoQuery (
+    @Then("^I should be able search (\\d+) documents for the \"([^\"]*)\" by bounding box query with points \\((-?\\d+), (-?\\d+)\\) and  \\((-?\\d+), (-?\\d+)\\) on field \"([^\"]*)\"$")
+    public void i_should_get_the_documents_for_the_in_the_Elastic_Search_by_geoQuery(
             int expectedCount, String index, Double topLatitude, Double topLongitude, Double bottomLatitude, Double bottomLongitude, String field) throws Throwable {
         super.i_should_get_the_documents_for_the_in_the_Elastic_Search_by_geoQuery(expectedCount, index, topLatitude, topLongitude, bottomLatitude, bottomLongitude, field);
     }