(InSAR) `configFiles` metadata field populated with `"None"`

In the five InSAR products (RIFG, RUNW, GUNW, ROFF, GOFF), the field metadata/processingInformation/inputs/configFiles is currently being populated with the string "None".

RSLC, GSLC, and GCOV populate that field with the filename of the granule's input runconfig file. Here are examples from X05016:

• RSLC: /data/work/jobs/2026/06/08/12/45/SCIFLO_RSLC__pcm_r05.01.4_pge_r05.01.6-track_frame_009_148_024_0_state-config-20260606T195428.345690Z-20260606T195428.377046Z/RunConfig.yaml

• GSLC: /data/work/jobs/2026/06/08/11/48/SCIFLO_GSLC__pcm_r05.01.4_pge_r05.01.6-gcov_gslc_001_149_080_full_individual_L_20_QP_05_QP_0_state-config-20260608T114806.410573Z/RunConfig.yaml

• GCOV: /data/work/jobs/2026/02/10/12/28/SCIFLO_GCOV__pcm_r05.00.8_pge_r05.00.9-gcov_gslc_009_120_072_partial_individual_L_20_QP_05_QP_28_state-config-20260210T122821.19475Z/RunConfig.yaml

For consistency between the products, should:

• Option A: InSAR should populate that field with the runconfig filename, or
• Option B: RSLC, GSLC, GCOV should instead populate that field with the string "None"
• Option C: configFiles should be removed entirely from the product spec. (As-is, does it offer value to the user?)
• Option D: ...?

cc: @hfattahi @xhuang-jpl @seongsujeong @jungkyoJung

Compare how metadata/processingInformation/inputs/configFiles is populated for the five InSAR products (RIFG, RUNW, GUNW, ROFF, and GOFF) against RSLC, GSLC, and GCOV. Confirm the intended consistency or removal approach, then verify that the selected behavior is reflected in the generated product metadata.