Description of problem (please be detailed as possible and provide log
snippests):

The `ocs-osd-removal-job` should generate unique names for each job. This feature would eliminate the need to delete the older/existing job when triggering the job for a second time. The user can directly proceed to the next disk replacement.



Version of all relevant components (if applicable):


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?


Can this issue reproduce from the UI?

In case of UI, only one osd can be replaced at a time. With unique job names, one doesn't have to delete the older job after the first osd replacement.

If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info:

1. Once this feature is added, the admin can run `oc process` command to trigger the job without deleting the older/existing jobs in the cluster.
2. One template (ocs-osd-removal) will create multiple jobs.
3. This feature will need documentation efforts for the relevant OCS versions (below OCS 4.9)