Fix: Handle double values in forcedVariationsMap

[vazarkevych]

Fix: Handle Double Values in Forced Variations

Overview

This PR makes forced variation parsing tolerant of numeric values that come from JSON deserialization as Double instead of Integer.

Previously, forced variation values were assumed to be integers. When values originated from JSON or other external sources, whole-number values could be represented as 1.0, which was not handled consistently.

What Changed

• Added normalization for forced variation maps.
• Supports numeric values represented as:
  • Integer
  • Long
  • BigInteger
  • BigDecimal
  • Double
  • Float
  • Gson numeric JsonPrimitive
• Converts whole-number doubles such as 1.0 to 1.
• Rejects unsupported values without crashing:
  • strings
  • booleans
  • objects
  • fractional values like 1.5
  • NaN / Infinity
  • values outside the integer range
• Keeps public forced variation getters as Map<String, Integer> for backward compatibility.