Small fix in jvmStats test

Removing second use of the `frequentyl()` function. This function is alraedy used in the
beginning of the testing block immediately after the declaration of `jvmStats` variable.
The second use of the `frequently()` could cause all the other variables that were carefully
prepared for the constructor to not be used at all.

Signed-off-by: Lukáš Vlček <lukas.vlcek@aiven.io>

server/src/test/java/org/opensearch/action/admin/cluster/node/stats/NodeStatsTests.java

@@ -682,8 +682,7 @@ public static NodeStats createNodeStats(boolean remoteStoreStats) throws IOExcep
                 );
             }
             JvmStats.Classes classes = new JvmStats.Classes(randomNonNegativeLong(), randomNonNegativeLong(), randomNonNegativeLong());
-            jvmStats = frequently()
-                ? new JvmStats(
+            jvmStats = new JvmStats(
                     randomNonNegativeLong(),
                     randomNonNegativeLong(),
                     new JvmStats.Mem(
@@ -698,8 +697,7 @@ public static NodeStats createNodeStats(boolean remoteStoreStats) throws IOExcep
                     garbageCollectors,
                     randomBoolean() ? Collections.emptyList() : bufferPoolList,
                     classes
-                )
-                : null;
+                );
         }
         ThreadPoolStats threadPoolStats = null;
         if (frequently()) {