Support defaults based on tables

[ctmay4]

Closes #117

Schema inputs currently only support default for setting inputs to a static value when not supplied by the caller. This pull request adds a new field called default_table to the input entity.

When staging a case:

• If default is supplied, it is used and default_table is ignored.
• Otherwise if default_table is specified as a table identifier then the table will be matched using the current context of supplied values. If there is a match and the input key has a VALUE in the list list of matched endpoints, the default value will be set. If a match is not found, an error will be added to the execution.

Tables created to be used as a default_table must:

• have an endpoint that maps to the input key it is being used with
• have a fall-through condition so that there is always a match (otherwise errors will be produced during the run); the fall-through can be a blank value if desired

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
88.5% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud