Refactor index refresh logic

Instead of refreshing all indices, which could lead to a warning when a system index is refreshed and cause the test to fail due to the unexpected warning, I modified the logic to refresh only the required 'test' index.

Signed-off-by: rithin-pullela-aws <[email protected]>

src/test/resources/rest-api-spec/test/fstore/80_search_w_partial_models.yml

@@ -18,6 +18,9 @@ setup:
         id:     2
         body:   { "field1": "v1 aoeu", "field2": " ua u v2", "field3": "foo bar text", "user_rating": 0.0  }
 
+  - do:
+      indices.refresh: { test }
+
   - do:
           allowed_warnings:
             - "this request accesses system indices: [.ltrstore], but in a future major version, direct access to system indices will be prevented by default"
@@ -67,11 +70,6 @@ setup:
 
 # Model only uses a single feature... although feature set has multiple
 
-  - do:
-      allowed_warnings:
-        - "this request accesses system indices: [.plugins-ml-config], but in a future major version, direct access to system indices will be prevented by default"
-      indices.refresh: {}
-
   - do:
         allowed_warnings:
           - "this request accesses system indices: [.ltrstore], but in a future major version, direct access to system indices will be prevented by default"
@@ -135,11 +133,6 @@ setup:
                     feature2: 2.3
                     no_param_feature: 3.0
 
-  - do:
-      allowed_warnings:
-        - "this request accesses system indices: [.plugins-ml-config], but in a future major version, direct access to system indices will be prevented by default"
-      indices.refresh: {}
-
 ---
 "single feature ranklib model":
   - skip: