✨ chore(crd): Add a named EmbeddedObjectMeta type when generateEmbeddedObjectMeta is enabled

[camilamacedo86]

Problem

CRD schemas did not clearly show which fields were embedded ObjectMeta.

You had to guess by matching field names (name, namespace, labels, etc).

Solution

When generateEmbeddedObjectMeta=true:

• Embedded ObjectMeta is generated as a named type
• New type: EmbeddedObjectMeta
• Can be identified directly (no guessing)

---

Example

Before (anonymous)

type MyResource struct {
    Template corev1.PodTemplateSpec `json:"template"`
}

After (named type)

type MyResource struct {
    Template corev1.PodTemplateSpec `json:"template"`
}

Generated schema:

• Registers EmbeddedObjectMeta type
• Example:

TypeIdent{Name: "EmbeddedObjectMeta", Package: metav1}

Closes: #805

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: camilamacedo86
Once this PR has been reviewed and has the lgtm label, please assign alvaroaleman for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment