New Frappé error code for NATS communication issues

[cv711]

One more beverage for the list: Frappé

[deepakprabhakara]

Change Frappé -> Frappe.
Why regenerate the files again? Let's roll it back to what it was.

[deepakprabhakara]

@cv711 Also document the new coffee code here - https://github.com/redsift/guide/wiki

[cv711]

• I saw Bombón in the list, that's why I went with the accent, will change it.
• If I don't run go generate how are files like internalstate_jsonenums.go going to be updated? The rest of the changes are mainly variables that were renamed and changes in the comments probably due to a newer version of the library.

[deepakprabhakara]

You only need changes from internalstate_string.go. What are the side effects of the changes to the errors (with the additonal wrapping from the new lib)? Are those fully tested on all the repos that use go-errs?

[cv711]

• The lib is backwards compatible and the only side effect is that some errors will have a bit more information to help with identifying their underlying cause. As you can see here the new internal type errWrapped will check if there are any additional information in the context to enhance the error or just print the error.
• Testing with prism there are no issues with these changes and for the rest of the repos they either use a Gopkg.lock or a go.sum to lock dependencies so it can be tested before their next release.