Automatically instantiate Spec and Status fields

[metacosm]

With 5.0.0, CustomResource are now parameterized with status and spec types allowing very compact, boilerplate-free definition of custom resource implementations. However, the status and spec fields are not currently automatically created which leads to awkward code to avoid NPEs.
The client should therefore attempt to instantiate the associated field where possible, provided the availability of a no-arg constructor for these types.