COO-1492: feat: update Perses and Perses operator versions

[jgbernalp]

This PR updates perses dependecies and includes the new v1alpha2 CRD version for Perses resources. A new resource PersesGlobalDatasource was added.

[openshift-ci-robot]

@jgbernalp: This pull request references COO-1492 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

This PR updates perses dependecies and includes the new v1alpha2 CRD version for Perses resources. A new resource PersesGlobalDatasource was added.

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 openshift-eng/jira-lifecycle-plugin repository.

[jan--f]

/lgtm
I guess the migration functionality isn't tested in our integrations suite? Is that worth adding or do we leave that to upstream?

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jan--f, jgbernalp

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [jan--f,jgbernalp]

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

[jgbernalp]

I guess the migration functionality isn't tested in our integrations suite? Is that worth adding or do we leave that to upstream?

Aside the upstream tests, @etmurasaki has the migration testing outlined, we will test manually first then add automation.