Fix Red Squiggles For Ralph

[carolynvs]

What does this change

The test for porter's schema was only checking that the schema was valid.
It wasn't checking that the porter.yaml validated against the schema... sad trombone

This fixes the test so that it fails when the schema drifts and prints all the problems with the schema.

• Add applyTo to parameters
• Use additionalProperties instead of patternProperties. PatternProperties validation is applied on top of properties, which isn't what we wanted. AdditionalProperties validation applies to properties not defined already in Properties.
• Use arrays instead of objects for credentials, parameters and outputs
• Remove destination nesting around env and path for parameter
• Remove explicit default for booleans when the value is false. Otherwise VS Code inserts those properties during autocomplete.

This requires a sweep of all our mixins because of the change from patternProperties to additionalProperties so that mixins also fix the double validation problem.

What issue does it fix

Closes #662

Notes for the reviewer

• Whenever the schema specifies a default value for a field, then when its autocompleted, then that field is always inserted with its default. e.g. if I type if - kubTAB, I'm going to get every single field that has a default inserted, even though those fields aren't necessary because those defaults are added at runtime by the mixin itself. We may want to stop adding defaults to the schema, so that that they aren't auto-inserted if that wasn't our intent.

Checklist

• Unit Tests
• Documentation
  • Documentation Not Impacted

[jeremyrickard]

LGTM. Love JSON Schema!