k6 Studio use default settings as fallback without informing the user

Steps to reproduce the problem

I don't know the exact steps, but I've stumbled upon it multiple times during development. Perhaps, saving a copy of your settings file and intentionally corrupting it may work?

In any case, when the file cannot be parsed, the default values will be used instead (incl. usage reporting preference)

Expected behaviour

The user should be informed about using default settings as a fallback.

Currently, It's also technically possible to access settings in code before the settings file is loaded. Consider improving the approach for loading settings to prevent this.

Actual behaviour

Default settings are used, but it may not be clear to the user.

Grafana k6 Studio version

any

OS

any