Extend code generator set functionality/directive

[Vandita2020]

Issue
This PR is related to fix the issue generating after executing PR #462

Summary
The PR helps in disregarding fields marked with set: ignore for nested fields. It also enhances the functionality of set:ignore to support the exclusion of fields from set_sdk.

Description

The PR fixes the issue coming after a new custom field is created and has set.ignore set to true for it. Even after setting the field to ignore, the field is getting used to set the SDK fields. In this case particularly, the new field was defined as shown below:

Code.S3SHA256:
        type: string
        set:  
          - method: Create
            ignore: true

And the issue it is causing is under sdk.go/newCreateRequestPayload function, where it is being set, as shown below:

if r.ko.Spec.Code.S3SHA256 != nil {
	f1.SetS3SHA256(*r.ko.Spec.Code.S3SHA256)
}

The goal is to ignore this particular line of code. And also to improve the basic functionality of set.ignore.

The set.ignore functionality was till now supporting exclusion of fields only when the field was used to set for the resource. This is when the set.from is also given, the set.from ignores the field coming from the resource. However when set.to is used, which is to ignore the field while setting SDK fields, the ignore didn't support that. This functionality got left behind because the set.to was added afterwards.

This PR added new way to set ignore. The ignore field can be set to from, to or all depending on whether you want to ignore setting the field for resource, or ignore the field for sdk, or for both, respectively.

So the above code will now look like:

Code.S3SHA256:
        type: string
        set:
        - method: Create
           ignore: "to"

Limitations
Currently this PR checks the set.ignore field only for members of the field whose type is structure.

Acknowledgment
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[ack-prow]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[a-hilaly]

/retest

[a-hilaly]

/test all

[Vandita2020]

/test dynamodb-controller-test

[Vandita2020]

/test dynamodb-controller-test

[a-hilaly]

Thank you @Vandita2020 - looks like this PR have some changes that we reviewd in #462 . Can you please delete the first 4 commits in this branch?
/hold

[Vandita2020]

/test s3-controller-test

[Vandita2020]

/test ec2-controller-test

[a-hilaly]

/test all

[a-hilaly]

/retest all

[ack-prow]

@a-hilaly: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

• /test acm-controller-test
• /test apigatewayv2-controller-test
• /test cloudfront-controller-test
• /test documentdb-controller-test
• /test dynamodb-controller-test
• /test ec2-controller-test
• /test ecr-controller-test
• /test efs-controller-test
• /test eks-controller-test
• /test eventbridge-controller-test
• /test iam-controller-test
• /test lambda-controller-test
• /test pipes-controller-test
• /test prometheusservice-controller-test
• /test s3-controller-test
• /test unit-test

The following commands are available to trigger optional jobs:

• /test s3-olm-test

Use /test all to run all jobs.

In response to this:

/retest all

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[a-hilaly]

/test all

[a-hilaly]

/retest

[a-hilaly]

/test all

[a-hilaly]

/test all

[a-hilaly]

/retest

[Vandita2020]

/test s3-olm-test

[a-hilaly]

Great stuff~
/lgtm

[ack-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: a-hilaly, Vandita2020

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [a-hilaly]

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

[a-hilaly]

/unhold