Better error handling at VMAccessLinux extension

Is it possible to include a better error handling at VMAccessLinux extension when customer tries to use it from az extension set command and missing the --protected-settings parameter?
I was helping a customer here who reported that was failing to run VMAccessLinux extension and I end up seeing that he was trying to run the extension by using the az vm extension set, however he was missing the parameter --protected-settings. I reproduced the exactly same error he was getting here:


I understand that people should be able, assume that if we want to use VMAccessForLinux extension, we need to provide password reset info and this is documented, but, in case of any person that is not paying attention, maybe having a better error handling at this scenario replying back with something like "you have missed --protected-settings" would cover that and don't make the person think that something else much more worse is happening due to we see a python error.

Reproduce the VMAccessLinux failure using the `az vm extension set` entry point without `--protected-settings`, then trace the extension's error path. Done means the missing parameter produces a clear message identifying `--protected-settings` instead of a Python error.

Written by the indexing model from the issue text.