Add owner references to Elyra role binding when creating notebooks

[DaoDaoNoCode]

Closes #1721

Description

Check the Elyra service account role binding every time we create/restart a notebook with the enabled pipelines feature. If the role binding is there, check the ownerReferences field to see if the notebook is the owner, if not, patch it. If the role binding is not there, create a new one with the ownerReferences field and set the notebook as the owner. In this way, every time the user deletes the notebook, it will also delete the role binding.

How Has This Been Tested?

1. Enable pipelines
2. Create a workbench
3. Check the role binding named elyra-pipelines-${workbenchName} is created and has the ownerReferences field
4. Try to delete the workbench, make sure the role binding is also deleted along with the deletion of the workbench
5. Create a workbench again, then remove the ownerReferences field in the role binding
6. Delete the workbench, you will find the role binding is not deleted
7. Then create a workbench with the same name in step 5
8. Check the role binding and you will find it's patched with the ownerReferences field again with the new workbench uid
9. Delete the workbench, and make sure the role binding is deleted too
10. Repeat step 5
11. Stop the workbench, then restart it
12. You will find the ownerReferences field is added
13. Toggle the status, make sure the role binding is not affected and no error out

Test Impact

N/A, it's about a field in role binding,

Request review criteria:

Self checklist (all need to be checked):

• The developer has manually tested the changes and verified that the changes work
• Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

• Included any necessary screenshots or gifs if it was a UI change.
• Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

• The developer has tested their solution on a cluster by using the image produced by the PR to main

[christianvogt]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: christianvogt

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [christianvogt]

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