Default requireApproverJustification to false before diffing

[maqiuyujoyce]

Change description

Fixes the issue that there is always a diff when spec.ApprovalWorkflow.ManualApprovals.RequireApproverJustification is set to false in the KCC manifest. This issue happens because false is the default value for this field, and the default value is not returned by the PAM API.

Supported no change step for PrivilegedAccessManagerEntitlement to verify this change in mock test. (Credit to #3045 by @acpana.)

Also updated the testdata version for PAM from v1alpha1 to v1beta1.

Tests you have done

• [N/A] Run make ready-pr to ensure this PR is ready for review.
• Perform necessary E2E testing for changed resources.

[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 ask for approval from maqiuyujoyce. 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

[yuwenma]

Could you add a test to reflect this change?

[maqiuyujoyce]

Could you add a test to reflect this change?

Done!

[yuwenma]

Could you add a test to reflect this change?

Done!

I saw you changed the test infra for PAM. We cannot do it because 1. if it is an infra change, we should PR review the infra separately and add test coverage to validate the infra change; 2. Adding If PAM then X, other Y in the core test infra introduces a big maintenance tech debt and should be avoided 3. The actual test suite still does not reflect how the PAM default behavior is changed before and after the code change.

I suggest we add a scenario test, and design the steps that can reflect the expected outcome of this fix.