Fix security plugin health API compatibility with OpenSearch 3.2.0+

Add Settings field to HealthResp struct to handle security plugin
configuration settings returned in the health API response. The settings
field contains security-related configuration like cache TTL settings.

Fixes test failures where the settings field was being dropped during
JSON unmarshalling, causing jsondiff mismatches in OpenSearch 3.2.0+.

Signed-off-by: Sean Chittenden <sean.chittenden@crowdstrike.com>

Author: sean-

CHANGELOG.md

@@ -19,6 +19,7 @@ Inspired from [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
 - Fix indices stats API compatibility with OpenSearch 3.2.0+ by adding max_last_index_request_timestamp and startree query fields
 - Fix cat APIs compatibility with OpenSearch 3.2.0+ by adding indexing timestamp and startree query fields
 - Fix floating point precision loss in nodes stats concurrent_avg_slice_count field by changing from float32 to float64
+- Fix security plugin health API compatibility with OpenSearch 3.2.0+ by adding settings field
 
 ### Security
 

plugins/security/api_health.go

@@ -48,9 +48,10 @@ func (r HealthReq) GetRequest() (*http.Request, error) {
 
 // HealthResp represents the returned struct of the health get response
 type HealthResp struct {
-	Message  *string `json:"message"`
-	Mode     string  `json:"mode"`
-	Status   string  `json:"status"`
+	Message  *string                `json:"message"`
+	Mode     string                 `json:"mode"`
+	Status   string                 `json:"status"`
+	Settings map[string]interface{} `json:"settings"` // Available in OpenSearch 3.2.0+
 	response *opensearch.Response
 }