feat(1-1-restore): add unpin-agent-cpu flag

[VAveryanov8]

This adds support of unpin-agent-cpu flag to 1-1-restore command.
Unpinning agent CPU should help with agent download speed.

Refs: #4375

---

Please make sure that:

• Code is split to commits that address a single change
• Commit messages are informative
• Commit titles have module prefix
• Commit titles have issue nr. suffix

[Copilot]

Pull Request Overview

This PR adds support for the unpin-agent-cpu flag to the 1-1-restore command to potentially improve agent download speed. Key changes include:

• Adding a new boolean flag (UnpinAgentCPU) in the Target model and corresponding command structures.
• Implementing CPU pinning/unpinning logic in the restore workflow and its helper functions.
• Documenting the new flag in both YAML configuration files and command usage partials.

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
pkg/service/one2onerestore/worker.go	Implements CPU pinning logic with deferred re-pinning behavior.
pkg/service/one2onerestore/model.go	Adds the UnpinAgentCPU field to the Target struct.
pkg/command/one2onerestore/cmd.go	Introduces a new flag and propagates its value into task props.
pkg/command/one2onerestore/res.yaml	Documents the new flag in the command resource configuration.
docs/source/sctool/partials/sctool_restore_1-1-restore_update.yaml	Updates command option documentation with the new flag.
docs/source/sctool/partials/sctool_restore_1-1-restore.yaml	Mirrors the update in a separate YAML partial for restore.

Comments suppressed due to low confidence (1)

pkg/service/one2onerestore/worker.go:82

• Consider using the original or a derived context instead of context.Background() in this deferred call for consistent cancellation handling and logging.

defer func() { if err := w.pinAgentCPU(context.Background(), workload, true); err != nil { w.logger.Error(ctx, "Can't pin agent to CPU", "error", err) } }()

[Michal-Leszczynski]

Maybe there won't be a need for this flag to be configurable (e.g. it will always be better to unpin agent for the 1-1-restore), but it is useful for benchmarking (it can always be removed before release if necessary).

FYI @mikliapko it is set to false by default, so it needs to be manually set during the 1-1-restore benchamarks.