APIRule v2 introduction

[strekm]

Description

Introduce v2 version that is the same as already introduced v2alpha1. There should not be any differences between v2alpha1 and v2 from API, conversion and functional point of view. Storage version stays as v1beta1. Conversion should be extended to v2 on same rules. Zero downtime migration should be supported as well. v2 version should be covered by int and e2e tests.

ACs:

• APIRule v2 introduced
• migration from v1beta1 to v2 is covered

PR:

• feat: APIRule v2 introduction #1663

TODO:

• v2 introduced in the CRD (by alias) [only alias was not enough]
• check for kubectl get calls (might need to be adapted to particular version)
• e2e v2alpha1 to v2
• e2e smoke test with happy path for v2

DoD:

• Provide unit and integration tests.
• Provide documentation.
• Verify if the solution works for both open-source Kyma and SAP BTP, Kyma runtime.
• If you changed the resource limits, explain why it was needed.
• Verify that your contributions don't decrease code coverage. If they do, explain why this is the case.
• Add release notes.