Refactor Restore controller with kubebuilder

[blackpiglet]

Describe the problem/challenge you have
[A description of the current limitation/problem/challenge that you are experiencing.]
A sub task of epic #2597 to refactor Restore controller with kubebuilder.

Describe the solution you'd like
[A clear and concise description of what you want to happen.]

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

• Velero version (use velero version):
• Kubernetes version (use kubectl version):
• Kubernetes installer & version:
• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release):

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

• 👍 for "The project would be better with this feature added"
• 👎 for "This feature will not enhance the project in a meaningful way"

[reasonerjt]

Per discussion we may have limited bandwidth to handle the refactor for restore controller, moving it out of v1.10

[blackpiglet]

After checking the backup and restore controller code, I think we can separate the VSL client, backup lister, getter, and other related client-go client into a sub-task, but there is not much other things can be splitted, and I think maybe there could be not that much effort as we expected for these two controllers, because many functions are not related to the kubebuilder, and the process shoule be similar to other controllers refactor PR.

[blackpiglet]

Phase 1 of removing the unneeded client is done, but there is still phase 2 to adopt the controller-runtime framework.