18738 FIX OTel: Fix collector memorylimit values

The memory_limiter processor expects limit_mib and spike_limit_mib to be in Mebibytes. Currently, we are passing raw byte values, causing the collector to set limits that are $1024^2$ times higher than intended. This PR adds a conversion constant to ensure values are correctly scaled to MiB.

CMK-28868

Change-Id: I3caa9855b744276ff70622681c46cbb89fd12165

Author: ramadanKhalifa

.werks/18738.md

@@ -0,0 +1,26 @@
+[//]: # (werk v2)
+# OTel: Fix collector memorylimit values
+
+key        | value
+---------- | ---
+date       | 2026-01-13T15:53:45+00:00
+version    | 2.6.0b1
+class      | fix
+edition    | cce
+component  | checks
+level      | 1
+compatible | yes
+
+The `memory_limiter` processor expects the parameters `limit_mib` and `spike_limit_mib` to be specified in **Mebibytes (MiB)**.
+
+Currently, raw byte values are being passed instead.
+This causes the collector to set memory limits that are 1,048,576 times higher than intended, which may prevent effective memory limiting and potentially lead to excessive memory usage by the collector.
+
+This update introduces a conversion constant to correctly scale the input values to MiB.
+As a result, memory limits will now be enforced as expected.
+
+
+### Action Required
+
+To ensure these corrected limits are applied to your environment, affected users should perform a **minor "dummy" change** (such as adding a comment) to the OpenTelemetry configuration.
+This will trigger a refresh of the YAML configuration and activate the updated scaling logic.