fix(mc): upgrade version

[jumana-s]

Description

What your PR adds/fixes/removes

Closes #333

Tests / Quality Checks

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 (e.g. k8scc01covidacr.azurecr.io/machine-learning-notebook-cpu:746d058e2f37e004da5ca483d121bfb9e0545f2b)?

[Jose-Matsuda]

LGTM was able to do on both dev and prod basic commands like mc alias , mc ls, mc cp mc mv mc rm mc mirror seemed to work without a hitch. (used image tag 78a9b939 as thats what I saw in the ci as I was getting issues using a63a6fb