[Request]: Add drivers to `container volume` for network NFS or SMB shares

### Feature or enhancement request details

For example:

- `container volume create --driver smb ...`
- `container volume create --driver nfs ...`

Create the SMB volume once:

```
container volume create --driver smb \
--opt share=//server/share \
--opt username=user \
--opt password=secret \
myshare
```

Use it exactly like any other named volume:

```
container run -v myshare:/data alpine ls /data
```

or with container create:

```
container create -v myshare:/data --name mycontainer alpine
```

This would make mounts not hop in the virtiofs.

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

Start with the `container volume create` command and compare it with the `container run` and `container create` volume paths. Done means named volumes can be created with SMB or NFS drivers and mounted through the examples shown, without routing mounts through virtiofs.

Written by the indexing model from the issue text.