Simplified AMV bufr2ioda.py input/output

[HuiLiu-NOAA]

This PR simplifies the input and output parameters with only $CDATE left in the json file.

For the cycle 2024052700, the brief available AMVs information generated by this python bufr2ioda_satwnd tool is listed below:

    Total AMV number over CONUS = 12612

Available variables:
$~~~~~~~~~~~$ dataProvider
$~~~~~~~~~~~$ dateTime
$~~~~~~~~~~~$ latitude, longitude, pressure

$~~~~~~~~~~~$ prepbufrReportType:
$~~~~~~~~~~~$ 245, $~~~~~~~~~~~$ 246, $~~~~~~~~~~~$ 247
$~~~~~~~~~~~$ GOES IR, WV cloud top, WV deep layer
$~~~~~~~~~~~$ 60% $~~~~~~~~~~~$ 30% $~~~~~~~~~~~$ 10% (of total AMVs)

$~~~~~~~~~~~$ satelliteIdentifier (= prepbufr subtype):
$~~~~~~~~~~~$ 270 (GOES 16), $~~~$ 272 (GOES 272)

     qiWithoutForecast,  percentErrorEE, windQualityMarker
     satelliteZenithAngle
     trackingCorrelation
     windCalculationMethod
     channelCentralFrequency
     coefficientOfVariation

$~~~~~~~~~~~$ ObsValue
$~~~~~~~~~~~$ windDirection
$~~~~~~~~~~~$ windEastward
$~~~~~~~~~~~$ windNorthward
$~~~~~~~~~~~$ windSpeed

$~~~~~~~~~~~$ ObsError
$~~~~~~~~~~~$ windEastward
$~~~~~~~~~~~$ windNorthward

[SamuelDegelia-NOAA]

Is there a reason we want to remove the input and output directories options (dump_dir and ioda_dir)? It seems to me that keeping these as arguments passed in by run_bufr2ioda.sh would be easier. But maybe this is already handled in rrfs-workflow?

From Hui:

Yes, the paths are already handled in the workflow, for all obs types in data/obs/.

[ShunLiu-NOAA]

@keenaneure @hu5970 and @guoqing-noaa Please review this PR if you have a chance. We will merge this one by the end of Friday.

[keenaneure]

Looks good to me.