Fix floating point precision loss in nodes stats API

Change ConcurrentAVGSliceCount field from float32 to float64 in nodes
stats API response to prevent precision loss. This fixes test failures
where values like 1.6666666666666667 were being truncated to 1.6666666
due to float32 precision limits.

Resolves OpenSearch 3.2.0+ compatibility issues with nodes stats API
floating point values.

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

Author: sean-

CHANGELOG.md

@@ -18,6 +18,7 @@ Inspired from [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
 - Fix nodes stats API compatibility with OpenSearch 3.2.0+ by adding max_last_index_request_timestamp and startree query fields
 - 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
 
 ### Security
 

opensearchapi/api_nodes-stats.go

@@ -157,7 +157,7 @@ type NodesStatsIndices struct {
 		ConcurrentQueryTotal        int     `json:"concurrent_query_total"`
 		ConcurrentQueryTimeInMillis int     `json:"concurrent_query_time_in_millis"`
 		ConcurrentQueryCurrent      int     `json:"concurrent_query_current"`
-		ConcurrentAVGSliceCount     float32 `json:"concurrent_avg_slice_count"`
+		ConcurrentAVGSliceCount     float64 `json:"concurrent_avg_slice_count"`
 		StartreeQueryTotal          int     `json:"startree_query_total"`          // Available in OpenSearch 3.2.0+
 		StartreeQueryTimeInMillis   int     `json:"startree_query_time_in_millis"` // Available in OpenSearch 3.2.0+
 		StartreeQueryCurrent        int     `json:"startree_query_current"`        // Available in OpenSearch 3.2.0+