Validate configs based on most primitive JSON types

[maddenp-noaa]

Synopsis

Support validation (via CLI or API) of configs of bool, dict, float, int, list, or str types -- basically, all primitive JSON types except for null. Previously, validation of only dict-based configs was supported. Internally, driver and fs-mode configs remain dict-based, and for now YAMLConfig continues to support only dict-based configs, though this could be similarly generalized later.

A config value with str type was perviously interpreted as a path to a file containing the config data to validate, so supporting str-based configs required splitting the former config argument into config_data and config_path, where a str value passed in to the former represents the config data itself, and a str value passed in to the latter continues to represent a path to a file.

Type

• Documentation
• Enhancement (adds new functionality)

Impact

• This is a breaking change (changes existing functionality)

Checklist

• I have added myself and any co-authors to the PR's Assignees list.
• I have reviewed the documentation and have made any updates necessitated by this change.

[NaureenBharwaniNOAA]

This looks great!