Multi-selecting URP assets resets the first asset's authored upscaler options to defaults and points the other selected assets at the replacement

Steps to reproduce:
1. Create new Unity project using Universal 3D Template
2. Open Project Settings → Player → Other Settings → Scripting Define Symbols
3. Add ENABLE_UPSCALER_FRAMEWORK, press Apply and let Editor recompile
4.  In PC_RPAsset.asset → Quality → Scaling Mode = Upscaling → Upscaler Priority → + → Spatial-Temporal Post-Processing.
5. Under its Spatial-Temporal Post-Processing foldout, change the Reactive Mask settings away from their defaults (e.g. Scale = 7.5, Apply Threshold = on, Threshold = 0.9.
6. In Mobile_RPAsset → Scaling Mode = Upscaling → Upscaler Priority → + → Auto (Bilinear or Nearest-Neighbor)
7. Save the project (Cmd/Ctrl+S).
8. In the Project window click PC_RPAsset, then Cmd/Ctrl-click Mobile_RPAsset so both are selected
9. Click PC_RPAsset on its own again and look at the Reactive Mask fields

Actual results: 
All three settings are back to their defaults. The options object was destroyed and recreated, its entity id changes and Mobile_RPAsset, which selects no upscaler with options at all, now holds a reference to that brand-new object living inside PC_RPAsset's file:

STPOptions defaults: reactiveOn=True  scale=1    applyThr=False  thr=0.2

BEFORE (PC selected alone)
PC_RPAsset      refs=1  entityId=47335:2816  owner=PC_RPAsset.asset  scale=7.5  applyThr=True   thr=0.9
Mobile_RPAsset  refs=0

AFTER (both selected, nothing touched)
PC_RPAsset      refs=1  entityId=47335:3328  owner=PC_RPAsset.asset  scale=1    applyThr=False  thr=0.2
Mobile_RPAsset  refs=1  entityId=47335:3328  owner=PC_RPAsset.asset  scale=1    applyThr=False  thr=0.2
                          ^^^^^^^^^^^^^^^^^^^ new object, authored values gone, and Mobile points at PC's copy

Expected results: PC_RPAsset still shows Scale 7.5 / Apply Threshold on / Threshold 0.9

Reproducible with versions: 6000.7.0b1, 7000.0.0a1

Can’t test with versions: 6000.0.84f1, 6000.3.24f1, 6000.5.11f1, 6000.6.2f1, 6000.7.0a6 (Feature doesn’t exist)

Tested on (OS): 

Notes: