Define a new EDPM role for installing nvidia driver on nodes

[sbauza]

In order to do nvidia vGPU testing, we need to deploy a specific package on EDPM nodes and do some other actions.
This is a multi-stage role requring a reboot between the two stages hence the two defined phases.

[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 cescgina 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

[openshift-ci]

Hi @sbauza. Thanks for your PR.

I'm waiting for a openstack-k8s-operators member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[github-actions]

Thanks for the PR! ❤️
I'm marking it as a draft, once your happy with it merging and the PR is passing CI, click the "Ready for review" button below.

[softwarefactory-project-zuul]

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/c18f1379352942ab958539d670a22b47

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 30m 40s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 17m 57s
❌ cifmw-crc-podified-edpm-baremetal RETRY_LIMIT in 27m 37s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 7m 48s
❌ cifmw-pod-pre-commit FAILURE in 5m 51s
✔️ cifmw-pod-zuul-files SUCCESS in 4m 08s
✔️ build-push-container-cifmw-client SUCCESS in 36m 27s
❌ cifmw-molecule-edpm_nvidia_mdev_prepare FAILURE in 4m 15s

[sbauza]

recheck

[SeanMooney]

/ok-to-test

[sbauza]

recheck

[hjensas]

How would customers do this?
Would they not use a custom service interface, or the bootstrap command interface so that this type of package install is handled using the products interfaces?

Here is an example custom service for repo setup: https://github.com/openstack-k8s-operators/install_yamls/blob/main/devsetup/edpm/services/dataplane_v1beta1_openstackdataplaneservice_reposetup.yaml

At first glance, I am very much against this change. We should use the products features to do this kind of thing.

@slagle - wdyt?