fix: Labels made observability metrics unusable

In traffic recording updates the labels were added to JFR events and this way they also got into the observability metrics. This made metrics with very high cardinality and overloads the server. We need to reconsider the approach to labels that get incorporated into the metrics.

Refs: #800

evita_engine/src/main/java/io/evitadb/core/metric/event/query/FinishedEvent.java

@@ -6,7 +6,7 @@
  *             |  __/\ V /| | || (_| | |_| | |_) |
  *              \___| \_/ |_|\__\__,_|____/|____/
  *
- *   Copyright (c) 2024
+ *   Copyright (c) 2024-2025
  *
  *   Licensed under the Business Source License, Version 1.1 (the "License");
  *   you may not use this file except in compliance with the License.
@@ -59,7 +59,6 @@ public class FinishedEvent extends AbstractQueryEvent {
 
 	@Label("Labels")
 	@Description("Zero or more client labels associated with the query. Labels are delimited by comma, label consists of name and value separated by equals sign.")
-	@ExportMetricLabel
 	private final String labels;
 
 	@Label("Query planning duration in milliseconds")