fix dynamicconfig parsing of long integers

[imilchev]

Problem

DynamicConfigToYamlDynamicConfig decoded CRD values via json.Unmarshal into an any, which always coerces JSON numbers to float64. A large integer like 2097152 became float64(2097152), and yaml.v3 then marshaled it in scientific notation (2.097152e+06). Temporal's file-based dynamic config client fails to parse this for settings that expect an integer.

Fix

• Added a test reproducing the scientific-notation bug (2097152 → value: 2097152).
• Added a test covering large integers nested inside objects/arrays.
• Updated existing table tests to expect int instead of float64 for integer values.

Note

This changes integer dynamic config values from float64 to int in YamlConstrainedValue.Value. Existing config maps holding values in scientific notation get rewritten once to the clean integer form on upgrade.

Fixes #517

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud