Fixed apply command resource definition yaml

[akijakya]

Q	A
Bug fix?	yes
New feature?	no
API breaks?	no
Deprecations?	no
Related tickets	-
License	Apache 2.0

What's in this PR?

Fixed generated resource definition yaml to be accepted by kubectl.

Why?

Currently when using kurun apply -f pod.yaml, the resource definition is incorrectly passed to the kubectl apply command because the runtime object is marshaled to yaml directly, resulting in something like this:

typemeta: # defines runtime property
  kind: Pod
  apiversion: v1
objectmeta: # defines runtime property
  selflink: ""
  ...

instead of this:

kind: Pod
apiversion: v1
...

Additional context

Tested locally.

Checklist

• Code meets the Developer Guide
• User guide and development docs updated (if needed)
• Related Helm chart(s) updated (if needed)