Adjust potential os.exit(1) for resource creation

[endzyme]

There is a call to config.GetConfigOrDie() in resource.go:123. This attempts to load the config, but if unsuccessful will call an os.Exit(1) from inside resourse.go.

From a user experience perspective it may be better to leverage config.GetConfig() and handle the err != nil by returning an empty ResourceProvider and an error message. Where this function is invoked, already has error handling which would capture a more usable message to the user instead of calling an os.Exit(1).