Plugin template: using wrong name in helm upgrade command difficult to troubleshoot

If you use the wrong name in the documented helm upgrade command, it causes the plugin to fail in a way that is hard to debug. The README does not state that the helm release name must match the plugin name in package.json!

The cryptic error you get in the UI is that the plugin entry does not load. Looking at the JavaScript console, you see the error:

Refused to execute script because its MIME type ('application/json') is not executable, and strict MIME type checking is enabled.

This makes you think that nginx is misconfigured, but it's really just a wrong plugin name. We should see if there is something we can do to make this better (either in the plugin template or console itself or both).