Add a way to configure restarted networking service name in reset.

[RomainMou]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change

/kind bug

/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
When running the reseting playbook, the networking service may be restart and there is no way to configure the name of the service.
The guessing is very basic and may not work in all cases (for example the Debian 12 cloud image use Netplan + Networkd by default).
This PR fixes that by letting the end-user the ability to manually configure the service name.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Add a variable reset_restart_network_service_name in the reset role to be able to configure the name of the service which is restarted.

[k8s-ci-robot]

Hi @RomainMou. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[yankay]

/ok-to-test

[floryut]

@RomainMou Thank you

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: floryut, RomainMou

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [floryut]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[RomainMou]

@RomainMou Thank you

My pleasure.

Sorry @floryut, this is my first PR here, so I'm not sure how the process works. Do I need to do something else for this PR or everything is ok?

[yankay]

Thanks @RomainMou

/lgtm

[floryut]

@RomainMou Thank you

My pleasure.

Sorry @floryut, this is my first PR here, so I'm not sure how the process works. Do I need to do something else for this PR or everything is ok?

Nothing PR needs 2 pair of eyes, one for approval of the change and "authorization" and one for lgtm of the codebase
You were missing the second one, done by @yankay yesterday and now automatically merge 👍