Missing input validation in config parameter enqueuing leads to silent configuration failures

The enqueueConfigChange function accepts configuration parameter changes without any validation at enqueue time. Invalid parameter values are only validated during the callback execution in _applyPendingConfigChanges(), where they are silently ignored rather than rejected. This creates a scenario where administrators can unknowingly submit incorrect values that either fail silently or cause unintended protocol behavior.

The following steps demonstrate the issue:

1. Admin submits a config change with an invalid value (e.g., price below minimum bounds)
2. The enqueueConfigChange function accepts this value without validation
3. During the next VRF callback, the invalid value is silently ignored in the setter function
4. The admin believes the change was applied but the protocol continues with old values
5. This creates a mismatch between expected and actual protocol configuration

1. Implement validation in enqueueConfigChange: Add input validation that reverts immediately for invalid parameter values, providing clear feedback to administrators.

2. Add parameter bounds documentation: Clearly document acceptable ranges for all configurable parameters.

Golden Grid: Confirmed.

Zealynx: Fixed.