Description of problem:

After upgrading OADP Operator from 1.1 to 1.2, both restic and node-agent Daemonsets are available in OADP 1.2 . As per Slack chat https://redhat-internal.slack.com/archives/C0144ECKUJ0/p1687484048906689?thread_ts=1687483682.777739&cid=C0144ECKUJ0, only `node-agent` Daemonset is required in OADP 1.2
I also have a Customer asking if old `restic` Daemonset isn't required in OADP 1.2, why did the operator did not take care of that on its own after the OADP 1.2 update?

Version-Release number of selected component (if applicable):
OADP 1.2

How reproducible:
Everytime

Steps to Reproduce:
1. Install RHOCP cluster
2. Install OADP 1.1.4 from OperatorHub
3. Enable `restic` from DataProtectionApplication CRD
4. Upgrade to OADP 1.2
5. In addition to `restic` Daemonset, there is also a new `node-agent` Daemonset seen in OADP 1.2

Actual results:

Both old `restic` and `node-agent` Daemonsets are seen after upgrading the operator from version 1.1.x to 1.2

Expected results:

If old `restic` Daemonset isn't required in OADP 1.2, this Daemonsets and all its pods should be automatically deleted after upgrading the operator from version 1.1.x to 1.2

Additional info:
This official documentation should also reflect the addition of `node-agent` Daemonset(and also the removal of `restic` Daemonset) in OADP 1.2+ versions.
https://docs.openshift.com/container-platform/4.12/backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.html#oadp-installing-dpa_installing-oadp-aws