HAS KNOWN FIX: FAIL LII2* COMPARE_base_no_interp due to fields VEGWP[LN,PD]

> ncview helps show the diffs in VEGWPLN (diffs in VEGWPPD are more subtle) with file1 (use_init_interp = .true.) on the left and file 2 on the right (no_interp):
> ```
> file 1=
> /glade/derecho/scratch/slevis/LII2FINIDATAREAS_D_P256x2_Ld1.f09_t232.I1850Clm60 BgcCrop.derecho_intel.clm-default.C.20251118_162221_1yxdza/run/LII2FINIDATAREAS
> _D_P256x2_Ld1.f09_t232.I1850Clm60BgcCrop.derecho_intel.clm-default.C.20251118_1
> 62221_1yxdza.clm2.h0a.0001-01-02-00000.nc.base
> file 2=
> /glade/derecho/scratch/slevis/LII2FINIDATAREAS_D_P256x2_Ld1.f09_t232.I1850Clm60 BgcCrop.derecho_intel.clm-default.C.20251118_162221_1yxdza/run/LII2FINIDATAREAS
> _D_P256x2_Ld1.f09_t232.I1850Clm60BgcCrop.derecho_intel.clm-default.C.20251118_1
> 62221_1yxdza.clm2.h0a.0001-01-02-00000.nc.no_interp
> ```
>
>

_Originally posted by @slevis-lmwg in [#3252](https://github.com/ESCOMP/CTSM/issues/3252#issuecomment-3550000272)_

**HISTORY**
- After ctsm5.3.059, LII2* started failing in RUN due to new finidat vs. old fsurdat (2025/6/24).
- The failure also occurred on the 5.4 branch in reverse, i.e. due to old finidat vs. new fsurdat as documented in #3252 (2025/6/12).
- The tests still fail in RUN on master (ctsm5.3.085) while the 5.4 branch remains in development. The tests stopped failing in RUN on the 5.4 branch when we updated to a consistent finidat/fsurdat pair, but proceeded to fail as expected in COMPARE_base_no_interp as explained in https://github.com/ESCOMP/CTSM/issues/3252#issuecomment-3192993166.
- We expected to fix the COMPARE_base_no_interp failure just before finalizing ctsm5.4 by following the instructions in the linked comment (just above). Instead we came across the [problem with VEGWP[LN,PD]](https://github.com/ESCOMP/CTSM/issues/3252#issuecomment-3549939151) shown with ncview above.

WHAT ELSE WE KNOW
- In discussing this with @olyson and @wwieder, Keith and I decided I should remove the two fields from restart. This enabled the LII2 tests to pass as explained in https://github.com/ESCOMP/CTSM/issues/3252#issuecomment-3554194101.
- However, now restart tests fail (e.g. ERS) suggesting that the two fields do need to be in restart for some reason.
- A lead (or a red herring?): Keith found that local-noon (LN) radiation fields do not go to restart, [but they also get reset to spval differently than VEGWPLN](https://github.com/ESCOMP/CTSM/pull/3613#issuecomment-3559972026).
- In another conversation about this, @ekluzek wondered whether the VEGWP[LN,PD] and the local-noon radiation fields should both be in restart, so as to restart correctly in sub-daily restarts.
- A detail that may implicate me in the source of the problem: I brought the h0a/h0i split to master in ctsm5.3.062, which may have broken these two fields while the LII2 tests were already labeled as expected failures.
- Keith tells me that the VEGWP[LN,PD] code was introduced by @djk2120, so I'm pinging Daniel here to keep you in the loop.

CURRENT PATH FORWARD
I got consensus from @olyson @ekluzek @wwieder to proceed with
- putting the VEGWP[LN,PD] fields back on restart
- removing from history and
- opening this issue

so as to proceed with ctsm5.4 work and resolve this at a later time.

FIX posted [below](https://github.com/ESCOMP/CTSM/issues/3617#issuecomment-3643437008).