add network_mode pasta parameter

Author: aimeeu

content/nomad/v1.11.x/content/plugins/drivers/podman.mdx

@@ -387,10 +387,11 @@ The `podman` driver implements the following [capabilities](/nomad/plugins/autho
   ```
 
 - `network_mode` - (Optional) Set the [network mode][network-mode] for the
-  container. By default the task uses the network stack defined in the task
+  container. By default, the task uses the network stack defined in the task
   group [`network`][nomad_group_network] block. If the groups network behavior
-  is also undefined, it will fallback to `bridge` in rootful mode or
-  `slirp4netns` for rootless containers.
+  is also undefined, it falls back to `bridge` in rootful mode, `slirp4netns`
+  for rootless containers on Podman version less than 5.0.0, or `pasta` for
+  rootless containers on Podman v5.0.0 or greater.
 
   - `bridge` - (Default for rootful) Create a network stack on the default
   Podman bridge.
@@ -399,9 +400,13 @@ The `podman` driver implements the following [capabilities](/nomad/plugins/autho
   container full access to local system services such as D-bus and is therefore
   considered insecure.
   - `none` - No networking.
-  - `slirp4netns` - (Default for rootless) Use `slirp4netns` to create a user
-  network stack. Podman currently does not support this option for rootful
-  containers ([issue][slirp-issue]).
+  - `pasta`: Use `pasta` to create a user network stack. This is the
+    default for rootless containers on Podman v5.0.0 or greater.
+  - `slirp4netns`: Use `slirp4netns` to create a user network stack. This is the
+  default for rootless containers on Podman versions less than 5.0.0. Podman
+  does not support `slirp4netns` for root containers. Refer to this [Podman
+  GitHub issue](https://github.com/containers/libpod/issues/6097) for an
+  explanation.
   - `task:name-of-other-task`: Join the network of another task in the same
   allocation.