Enhance partial explanations on catalogsource.status

[grokspawn]

Type of question

Are you asking about community best practices, how to implement a specific feature, or about general context and help around the operator-sdk?
Opening this on behalf of a support issue that came in around the lack of description elements for catalogsource.status (deploy/chart/crds/0000_50_olm_00-catalogsources.crd.yaml) especially w.r.t. catalogsource.status.configMapReference

Question

What did you do?
installed olm and ran k explain catalogsource.status

What did you expect to see?
descriptive text blobs for areas indicated in 'what did you see instead' section indicated by <no description> tags.

What did you see instead? Under which circumstances?
A clear and concise description of what you expected to happen (or insert a code snippet).

GROUP:      operators.coreos.com
KIND:       CatalogSource
VERSION:    v1alpha1

FIELD: status <Object>

DESCRIPTION:
    <empty>
FIELDS:
  conditions	<[]Object>
    Represents the state of a CatalogSource. Note that Message and Reason
    represent the original status information, which may be migrated to be
    conditions based in the future. Any new features introduced will use
    conditions.

  configMapReference	<Object>
    <no description>

  connectionState	<Object>
    <no description>

  latestImageRegistryPoll	<string>
    The last time the CatalogSource image registry has been polled to ensure the
    image is up-to-date

  message	<string>
    A human readable message indicating details about why the CatalogSource is
    in this condition.

  reason	<string>
    Reason is the reason the CatalogSource was transitioned to its current
    state.

  registryService	<Object>
    <no description>

Environment

• operator-lifecycle-manager version:
  v0.26.0

• Kubernetes version information:

Client Version: v1.29.1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.27.3

• Kubernetes cluster kind:
  kind