Do not mount /tmp into bazel container with shared mount propagation.
Do not mount /tmp into bazel container with shared mount propagation.

This is the same issue as described in moby/moby#36179.
If any of the other volumes mounted in the bazel container happen to be inside
/tmp, then they will be propagated to the host mount namespace, and hence never
cleaned up by docker on container destroy.

What's worse is that the number of leaked mounts increases exponentially. See
this reproducer:
```shell
$ mkdir /tmp/gvisor
$ docker run --rm -d --name=repro -v /tmp/gvisor:/tmp/gvisor -v "/tmp:/tmp:shared" ubuntu:focal /bin/sleep infinity
5690703c0f6128eebb38180c1bbb5b9ba83018affa284bc82d78a52860321f97
$ docker kill repro
repro
$ sudo cat /proc/self/mountinfo | grep gvisor
1914 29 254:1 /tmp/gvisor /tmp/gvisor rw,relatime shared:1 - ext4 /dev/mapper/glinux_20210409-root rw,errors=remount-ro,i_version
$ docker run --rm -d --name=repro -v /tmp/gvisor:/tmp/gvisor -v "/tmp:/tmp:shared" ubuntu:focal /bin/sleep infinity
11a7cfba501277e2b61fafa46c782fbd5829629dab91ff8ca0c589bdb1d63b24
$ docker kill repro
repro
$ sudo cat /proc/self/mountinfo | grep gvisor
1914 1946 254:1 /tmp/gvisor /tmp/gvisor rw,relatime shared:1 - ext4 /dev/mapper/glinux_20210409-root rw,errors=remount-ro,i_version
1950 1914 254:1 /tmp/gvisor /tmp/gvisor rw,relatime shared:1 - ext4 /dev/mapper/glinux_20210409-root rw,errors=remount-ro,i_version
1946 29 254:1 /tmp/gvisor /tmp/gvisor rw,relatime shared:1 - ext4 /dev/mapper/glinux_20210409-root rw,errors=remount-ro,i_version
$ docker run --rm -d --name=repro -v /tmp/gvisor:/tmp/gvisor -v "/tmp:/tmp:shared" ubuntu:focal /bin/sleep infinity
11a7cfba501277e2b61fafa46c782fbd5829629dab91ff8ca0c589bdb1d63b24
$ docker kill repro
repro
$ sudo cat /proc/self/mountinfo | grep gvisor
1914 2018 254:1 /tmp/gvisor /tmp/gvisor rw,relatime shared:1 - ext4 /dev/mapper/glinux_20210409-root rw,errors=remount-ro,i_version
1950 2014 254:1 /tmp/gvisor /tmp/gvisor rw,relatime shared:1 - ext4 /dev/mapper/glinux_20210409-root rw,errors=remount-ro,i_version
1946 2010 254:1 /tmp/gvisor /tmp/gvisor rw,relatime shared:1 - ext4 /dev/mapper/glinux_20210409-root rw,errors=remount-ro,i_version
2022 1950 254:1 /tmp/gvisor /tmp/gvisor rw,relatime shared:1 - ext4 /dev/mapper/glinux_20210409-root rw,errors=remount-ro,i_version
2018 1946 254:1 /tmp/gvisor /tmp/gvisor rw,relatime shared:1 - ext4 /dev/mapper/glinux_20210409-root rw,errors=remount-ro,i_version
2014 1914 254:1 /tmp/gvisor /tmp/gvisor rw,relatime shared:1 - ext4 /dev/mapper/glinux_20210409-root rw,errors=remount-ro,i_version
2010 29 254:1 /tmp/gvisor /tmp/gvisor rw,relatime shared:1 - ext4 /dev/mapper/glinux_20210409-root rw,errors=remount-ro,i_version
```

Eventually, docker becomes prohibitively slow and starts throwing ENOSPC errors randomly.

PiperOrigin-RevId: 480986037

google/gvisor,google/gvisor,google/gvisor,google/gvisor,google/gvisor,google/gvisor,google/gvisor,google/gvisor