checking for ambiguous csv formats

[shaselton-usds]

One line description of your change (less than 72 characters)

CSV format can be built in a way that the validator is unable to determine if it is a Wide or Tall format.

Problem

When the validator encounters a CSV format that is without Tall specific column headers: payer_name and plan_name as well as lacking any payer/plan combinations that are found in the Wide format, the validator's default behavior was to try to validate the CSV against the Wide format ruleset.

Solution

The validator now checks for both types of formats before doing any additional validation.

Result

The validator will now catch CSV files that do not have either a Tall or Wide format, throw an error, and inform the user to update their file to conform to either the Tall or Wide format.

Test Plan

Unit tests added to check functionality.

[mint-thompson]

This looks like it perfectly handles the "not enough columns to tell" ambiguous case. Do we also want to add handling for the "too many columns" ambiguous case, where we have the payer_name and plan_name columns, and also at least one set of payer-plan columns?

[eoverly]

Looks good. Thanks!

[shaselton-usds]

@mint-thompson updated to check for both wide and tall formats: ee9aa8f

[mint-thompson]

@mint-thompson updated to check for both wide and tall formats: ee9aa8f

Looks good, thank you!