Resetting a Volume override applies the in-progress field value instead of the default when the field has not been committed

Steps to reproduce:

1. Create a 3D URP new project via Unity Hub
2. Select PC_RPAsset.asset in the Project Browser
3. In the Inspector scroll down to the "Bloom" section
4. Change value for the "Threshold" property without pressing enter
5. Click the kebab menu icon for "Bloom" and select "Reset"
6. Observe the in-edit value

Actual results: The field ends up set to the value you were typing (your custom value), not the default. The Reset runs, but because the field was still being edited (not committed), the pending edit is applied on top of the reset, so the custom value wins and the override is not reset.

Expected results: Clicking the kebab menu should commit the focused field first (the field loses focus and its value is applied, as when clicking anywhere outside a field), and then Reset should set the override back to its default. The result must be the default value - Reset should reset, not set the in-progress value.

Reproducible with versions: 6000.0.0f1, 6000.0.84f1, 6000.3.24f1, 6000.6.1f1, 6000.7.0b1, 7000.0.0a1

Tested on (OS): Windows 11

Notes:

• Root cause: a focus/commit ordering issue - the context-menu Reset does not take keyboard focus away from the actively-edited field before executing, so the field's still-pending value write lands after the reset. Standard Unity behavior is that clicking outside a field commits it; the kebab click does not, so the reset is overwritten by the deferred field commit.