tool: allow Spec to map to Status or ObservedState in mapper generator

[jingyih]

In our codebase, some direct resources split a proto message into Spec and Status (as opposed to Spec and ObservedState). Example:

k8s-config-connector/apis/bigqueryconnection/v1beta1/connection_types.go

Lines 118 to 123 in dd2d99c

	type AwsPropertiesSpec struct {
	// Authentication using Google owned service account to assume into
	// customer's AWS IAM Role.
	// +required
	AccessRole *AwsAccessRoleSpec `json:"accessRole,omitempty"`
	}

k8s-config-connector/apis/bigqueryconnection/v1beta1/connection_types.go

Lines 233 to 236 in dd2d99c

	// +kcc:proto=google.cloud.bigquery.connection.v1.AwsProperties
	type AwsPropertiesStatus struct {
	AccessRole *AwsAccessRoleStatus `json:"accessRole,omitempty"`
	}

We should allow Spec to map to Status or ObservedState in mapper generator.

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

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

[jingyih]

/cc @jasonvigil

[yuwenma]

I think the BQCC AWSPropertyStatus is manually added.

[jingyih]

I think the BQCC AWSPropertyStatus is manually added.

Yeah, in @jasonvigil's output field design doc, the proposed naming convention is to append ObservedState.

This PR introduces a small update to ensure the mapper generator is compatible with the legacy naming conventions. A few Go structs in BQCC currently end with the suffix Status, and other resources might have also followed this pattern.