Disabling already disabled default-storageclass addon errors

[spowelljr]

How to reproduce:

# start minikube
$ minikube start

# disable default-storageclass once as it's enabled by default
$ minikube addons disable default-storageclass
🌑  "The 'default-storageclass' addon is disabled

# disable the already disabled default-storageclass addon
$ minikube addons disable default-storageclass

❌  Exiting due to MK_ADDON_DISABLE: run callbacks: running callbacks: [Error disabling standard as the default storage class: Error getting storage class standard: storageclasses.storage.k8s.io "standard" not found]

╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                                                         │
│    😿  If the above advice does not help, please let us know:                                                           │
│    👉  https://github.com/kubernetes/minikube/issues/new/choose                                                         │
│                                                                                                                         │
│    Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue.                                  │
│    Please also attach the following file to the GitHub issue:                                                           │
│    - /var/folders/9l/6wpxv6wd1b901m1146r579wc00rqw3/T/minikube_addons_f53b12e0586db40a2c65ab70e9c8eb17429ee251_0.log    │
│                                                                                                                         │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

Expected:

🌑  "The 'default-storageclass' addon is disabled

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale