[3pt] Add new arg for code version

[RobHanna-NOAA]

Can we add a new mandatory argument to CatFIM which askes for the code version we are running. Note.. not the hand version behind it, but the FIM code version. The format will be something like "CatFIM 2.2" or "CatFIM 2_2" (tbd). We need to add this as a new column to all output files (sites, library for SB and FB). This is a Derek request and other tools are going to pick up similar tools. Let's call this field "catfim_version". Also.. let's rename the "version" field, to "hand_version".

[CarsonPruitt-NOAA]

Will we always know at the time of running the CatFIM code what the final FIM version will be?

[RobHanna-NOAA]

Yes. Derek asked for a new "product" code version. When we build hand, we know it is 4.5.11.1 and put it in a field in the catfim outputs called "version". We need to rename this to hand_version. Then he wanted as new peice of data saying what code version of Catfim was used, ie) 2.2. When we load it into HV, we load the "public" version of FIM 5.1 (or whatever). Not sure when/how we will use this in the HV UI, but it is a quick add to our CatFIM code to open up that option. He asked for the same thing for probabilty/LoFi. Likely starting at something like 1.0 or something. So.. yes.. a third "version:" field but only for CatFIM and Probability. The output folders for HAND give that to use automatically. ie) HAND_4_5_11_1.