Issue Description

CondTag is replacing CondNumber in location file and being added to account file.
In the fm file generation, we need to base the grouping logic for items at the cond level on the CondTag field (currently it is based on the CondNumber). CondNumber is now only found in the account file and only used to identify the financial terms to apply at the cond level.
We should only have multiple CondTags per location when there are conditions of different CondPriorities and therefore multiple hierarchal levels.

Steps to Reproduce (Bugs only)

Version / Environment information

Example data / logs

examples to follow;

• single condition in new format
• single condition where terms vary by policy (different CondNumbers per layer, same CondTag, CondPriority1)
• multiple hierarchal conditions (CondPriority 1 and 2, multiple CondTags per location , multiple CondNumbers)
• invalid conditions example (to produce error message and fail)