Add bounds for metadata

Desired capability or behavior.

Add additional information to metadata to allow for specifying valid values for a given variable. This would be optional and allow Aviary to check if values in AviaryValues are within the valid bounds and raise an error if they are not. The limitation would be this check can only be done for input variables, and not calculated variables (outputs). We could have a check after the run (with warnings instead of errors??) to alert users if calculated values strayed outside of valid bounds.

Suggested implementation.

Add "minimum" and "maximum" fields to metadata. Add min/max bounds to all variables where that makes sense. Add new checks to AviaryValues alongside the typing checks to see that any value added to them is "allowable", raise and error or warning (depending on what we decide to implement) if they are not. Remove preprocessor checks that are replaced by this automated system.

Optionally look into a check after optimization on the final output. This could maybe be done by dumping every OM variable that exists in the hierarchy into an AviaryValues object to re-use the existing checks. That could then be spun into a report (the csv of the output AviaryValues, that could then be re-used for off-design runs).

Start by tracing metadata handling, AviaryValues typing checks, and the preprocessor checks that may be replaced. Identify how minimum and maximum fields would flow into validation for input variables, and separate the unresolved post-optimization output check from the core scope. Done should include bounds where appropriate and defined behavior for out-of-range values, including whether to raise errors or warnings.