Rename proto/v1beta1/Resource.Resource field to improve clarity

[pedjak]

There is a struct Resource containing field Resource. The doc says it is the json representation of the given resource. Could we rename the field to reflect that?

[negz]

Any suggestions on naming?

In a way I think the Resource field is accurate, it's more that the message it lives in represents not only a resource but its associated properties - e.g. connection details and readiness. So renaming the Resource message could be another option.

[pedjak]

Any suggestions on naming?

Since it contains the resource content encoded in json, perhaps we can call it JSONData?