API review: optionality

We have some places in the API where fields are optional (such as wasm), but they aren't actually technically optional (e.g. they are required, but they have a default). Part of this is because of how kube-api-linter works. The purpose of this spike is to dig into this a bit and see about good ways to handle this.