chore(e2e test) port 1-049_validate_logs_rbac_enforcement Kuttle test to Ginko

[aali309]

What type of PR is this?
This PR ports 1-49_validate_logs_rbac_enforcement to Ginko test

/kind enhancement

What does this PR do / why we need it:

Have you updated the necessary documentation?

• Documentation update is required by this PR.
• Documentation has been updated.

Which issue(s) this PR fixes:

Fixes #?

Test acceptance criteria:

• Unit Test
• E2E Test

How to test changes / Special notes to the reviewer:

[openshift-ci]

[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 anandf for approval. For more information see the 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

[aali309]

/retest-required

[aali309]

/retest

[openshift-ci]

@aali309: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/v4.17-kuttl-sequential	1249d1d	link	true	/test v4.17-kuttl-sequential
ci/prow/v4.19-kuttl-sequential	1249d1d	link	true	/test v4.19-kuttl-sequential
ci/prow/v4.19-e2e	1249d1d	link	true	/test v4.19-e2e
ci/prow/v4.19-kuttl-parallel	1249d1d	link	true	/test v4.19-kuttl-parallel

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.