Starting with version 8.2, maxIndexBuildMemoryUsageMegabytes treats values like 0.75 as 0.75 MB which is a silent behavior change from previous versions where the same value is interpreted as 75%.

This can make existing configs unexpectedly unusable or dramatically change index build performance when upgrading, so we should either document and guardrail this change in behavior or we shouldn't do it.