oci_load incompatible with older version of Podman

Nobody has claimed this yet.

I'm running Bazel v7.2.0, rules_oci v2.0.0 on an Ubuntu 22.04.5 LTS system. I've installed the Ubuntu package for podman which is currently v3.4.4.

My build uses `oci_load` to build and import containers into podman:

```
oci_load(
name = "foobar_tarball",
image = ":foobar_image",
repo_tags = ["foobar:latest"],
)
```

The resulting script fails to run:

```
$ bazel-out/aarch64-fastbuild/bin/foobar_tarball.sh
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Error: payload does not match any of the supported image formats (oci, oci-archive, dir, docker-archive)
tar: Write error
```

Looking into the issue, this appears to be a compatibility issue with how older versions of podman implement `podman load`. In particular the following two commands lines work differently:

```
# fails with "payload does not match any of the supported image formats"
podman load --input <(tar -c $FILES)
# succeeds and loads the image
tar -c $FILES | podman load
```

This issue appears fixed in newer versions of podman, however I haven't tracked down the details.

The fix is relatively straightforward; to change the `podman load` command line [oci/private/load.sh.tpl](https://github.com/bazel-contrib/rules_oci/blob/a002dafcddffecf5a670adaea53bcb7a4ee4eeb5/oci/private/load.sh.tpl#L31-L33)

Start with oci/private/load.sh.tpl around the podman load command and reproduce the generated foobar_tarball.sh behavior using Podman 3.4.4 on Ubuntu. Verify the resulting script loads the image successfully with the older Podman interface while preserving compatibility with newer versions.

Written by the indexing model from the issue text.