container/opts: Add bind-create-mountpoint mount option

[vvoland]

Add support for the bind-create-mountpoint option in bind mounts, which instructs the daemon to create the mountpoint directory inside the container if it doesn't exist.

This allows to replace the legacy -v /src/dir:/dst with the --mount.

Usage:
--mount type=bind,src=/host/path,dst=/container/path,bind-create-mountpoint
--mount type=bind,src=/host/path,dst=/container/path,bind-create-mountpoint=true

- What I did

- How I did it

- How to verify it

- Human readable description for the release notes

Add `bind-create-mountpoint` option to `--mount` flag for bind mounts.

- A picture of a cute animal (not mandatory but encouraged)

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[thaJeztah]

Oh! I now recall I saw a PR from @ndeloof which I think is doing the same, but I had to think about the naming of the option (he picked bind-create-host-path);

• introduce bind create-host-path option, aligned with docker-compose #6573

host path is probably more correct though, because it's creating the path on the host (if missing); destination path (inside the container) should always be created?

[vvoland]

I think it should be bind-create-mountpoint to match the API param. Perhaps we should rename it on the API level too?

[thaJeztah]

Yeah, we probably didn't think it through properly when we named the API field 😞. For the CLI, UX doesn't have to strictly match the API naming of course.

But yeah; ideally we'd rename the API field, but that may need some juggling to deprecate the old (so perhaps we'd need "both" for some time).

[thaJeztah]

Oh! Regardless of that; Nicolas's PR also has some documentation changes; if we continue on this PR, we should include those here (you can add him as co-authored-by).