Update postings in STATIC layers granule ID to decimeters

[nemo794]

Currently, the STATIC layers filenaming (and granule ID) convention follows this format, where XPosting and YPosting are in units of meters:
NISAR_IL_PROD_REL_P_FRM_XPosting_YPosting_ValidityStartDateTime_CRID_LOC_CTR.h5

For example, here the XPosting and YPosting are 10 meters and 10 meters:
NISAR_L2_STATIC_001_A_219_010_010_20220104T182346_S05000_J_001.h5

Issue: We need to allow for STATIC products that match 77MHz GSLC postings of 5m by 2.5m. The 2.5m creates a naming conflict, because the current convention only allows for integer multiples of 1 meter, not fractional meters.

Solution: In an offline discussion with @parosen , @hfattahi , and ASF, it was decided to update the STATIC layers granule ID (and thus, filenaming) convention to have the posting be in units of decimeters.

Example of updated 10 meters by 10 meters granule ID:
NISAR_L2_STATIC_001_A_219_0100_0100_20220104T182346_S05000_J_001.h5

Example of updated 5 meters by 2.5 meters granule ID:
NISAR_L2_STATIC_001_A_219_0050_0025_20220104T182346_S05000_J_001.h5

Cc: @gshiroma @hfattahi

[gshiroma]

Sounds good to me. Thank you, @nemo794 .