Mounted files using singleuser.extraFiles partially remain after re-naming

[M4C4R]

Bug description

When I mount a file using singleuser.extraFiles onto the user's home directory, then decide to rename the file using mountPath.
The old file remains when the user restarts their server, albeit it is empty.

How to reproduce

1. Download the latest release from https://hub.jupyter.org/helm-chart/ (3.0.3 for me), extract it, and change directory to it
2. Deploy the helm chart:

helm upgrade --install jupyterhub . \
--set singleuser.extraFiles.test.mountPath="/home/jovyan/test" \
--set singleuser.extraFiles.test.stringData="abc"

3. Launch a user's server using the UI and notice the file test exists
4. Re-name the file and deploy again:

helm upgrade --install jupyterhub . \
--set singleuser.extraFiles.test.mountPath="/home/jovyan/test2" \
--set singleuser.extraFiles.test.stringData="abc"

5. Restart the user's server and notice that there are now two files, one being the original, which is now empty.

Expected behaviour

I expected the original file to disappear as it is no longer being mounted.

Actual behaviour

The (now empty) file remains after being re-named.

Your personal set up

Distribution: zero-to-jupyterhub

I've observed this issue on a local Minikube cluster, as well as GKE on GCP.