fix: updated tmp_home copy script to prevent no space error

[mathis-marcotte]

Description

https://jirab.statcan.ca/browse/ZONE-269

Tests / Quality Checks

Tested on artifactory.cloud.statcan.ca/das-aaw-docker/jupyterlab-cpu:47e208c044060e2abf7449924d8f937c57ef2ee6

Tested with a new notebook that had a full workspace volume attached. (created the volume by making a new default notebook, and using fallocate to make a file that took up the entire volume's storage, then deleted that notebook to free up it's volume so that it could be attached as existing to a new notebook.

We see in the logs for this scenario that it did print out the available and needed space.

/package/admin/s6-overlay/libexec/preinit: info: /run belongs to uid 0 instead of 1000 - fixing it 
 s6-rc: info: service s6rc-oneshot-runner: starting 
 s6-rc: info: service s6rc-oneshot-runner successfully started 
 s6-rc: info: service fix-attrs: starting 
 s6-rc: info: service fix-attrs successfully started 
 s6-rc: info: service legacy-cont-init: starting 
 cont-init: info: running /etc/cont-init.d/01-copy-tmp-home 
 INFO: Available HOME space: '    0' 
 INFO: HOME_TMP space: '713196' 
 cont-init: info: /etc/cont-init.d/01-copy-tmp-home exited 0 
 cont-init: info: running /etc/cont-init.d/02-start-custom 
 --------------------Starting up--------------------  
...

Beta Process

• Should this branch target "beta"?

Are there breaking changes?

Ask yourself the next question;

• Do we want to maintain the previous image from which we had to do breaking changes from?

If no, then carry on. If yes, there is a breaking change and we want to maintain the previous image do the following

• Create a new branch for the current version (ex v1) based off the current master/main branch
• Increment the tag in the CI for pushes to master/main (v1 to v2)
• Change the CI that on pushes to the newly created "v1" branch (the name of the newly created branch we want to maintain is) it will push to the ACR.

Automated Testing/build and deployment

• Does the image pass CI successfully (build, pass vulnerability scan, and pass automated test suite)?
• If new features are added (new image, new binary, etc), have new automated tests been added to cover these?
• If new features are added that require in-cluster testing (e.g. a new feature that needs to interact with kubernetes), have you added the auto-deploy tag to the PR before pushing in order to build and push the image to ACR so you can test it in cluster as a custom image?

JupyterLab extensions

• Are all extensions "enabled" (jupyter labextension list from inside the notebook)?

VS Code tests

• Does VS Code open?
• Can you install extensions?

Code review

• Have you added the auto-deploy tag to your PR before your most recent push to this repo? This causes CI to build the image and push to our ACR, letting reviewers access the built image without having to create it themselves
• Have you chosen a reviewer, attached them as a reviewer to this PR, and messaged them with the SHA-pinned image name for the final image to test on the dev cluster (e.g. k8scc01covidacrdev.azurecr.io/jupyterlab-cpu:746d058e2f37e004da5ca483d121bfb9e0545f2b)?