[TASK] Restart capability for batching-based Optimizers/Samplers

[aalfonsi]

---

Issue Description

Is your feature request related to a problem? Please describe. For Optimizers/Samplers that use batching functionalities, the Restart (<Restart>) approach is not functional, since a specific implementation needs to be implemented.

Describe the solution you'd like Activation of the Restart for the Batching approach.

Describe alternatives you've considered N/A

---

For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

• [x] 1. Is it tagged with a type: defect or task?
• [x] 2. Is it tagged with a priority: critical, normal or minor?
• [x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
• [x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
• [x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

---

For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

• [ ] 1. If the issue is a defect, is the defect fixed?
• [ ] 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
• [ ] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
• [ ] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
• [ ] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

[aalfonsi]

This functionality is starting becoming an urgency. See #2061