[CI:DOCS] Update podman network docs

[radar07]

Update the podman network docs to specify that the default rootless networking tool has been swapped from slirp4netns to pasta.

Fixes: 22543

Does this PR introduce a user-facing change?

None

[radar07]

@Luap99, I made the changes as suggested. I noticed a few places in the tutorials where slirp4netns is mentioned as the default rootless network.

https://github.com/containers/podman/blob/main/docs/tutorials/rootless_tutorial.md https://github.com/containers/podman/blob/main/docs/tutorials/basic_networking.md https://github.com/containers/podman/blob/main/docs/tutorials/performance.md https://github.com/containers/podman/blob/main/docs/tutorials/performance.md

Should these be changed as well?

[Luap99]

@Luap99, I made the changes as suggested. I noticed a few places in the tutorials where slirp4netns is mentioned as the default rootless network.

https://github.com/containers/podman/blob/main/docs/tutorials/rootless_tutorial.md https://github.com/containers/podman/blob/main/docs/tutorials/basic_networking.md https://github.com/containers/podman/blob/main/docs/tutorials/performance.md https://github.com/containers/podman/blob/main/docs/tutorials/performance.md

Should these be changed as well?

yes

[packit-as-a-service[bot]]

Ephemeral COPR build failed. @containers/packit-build please check.

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lahwaacz, Luap99, radar07

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~~ [Luap99]

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

[mheon]

/lgtm

[Luap99]

/cherry-pick v5.1

[openshift-cherrypick-robot]

@Luap99: new pull request created: #22772

In response to this:

/cherry-pick v5.1

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-sigs/prow repository.