chore: misc prep for release with ES modules, yargs, and nexe builds

Author: rossiam

CHANGELOG.md

@@ -1,5 +1,21 @@
 # Change Log
 
+## 2.0.0
+
+* All commands now have examples in their help (`smartthings <command> --help`).
+* args that require enum-like types are now case-insensitive. e.g. You can now list zigbee devices
+  with `smartthings devices --type zigbee`.
+* The config file location is now determined by https://www.npmjs.com/package/env-paths[envPaths] library
+  rather than oclif. A reasonable attempt has been made at finding the old config and copying it for
+  the user so normally no change is needed other than making changes in the new file if necessary.
+  The `config` command now displays the name of the configuration file.
+* Commands that take a capability specification on the command line now get the version from a flag
+  rather than an argument. e.g. `smartthings capabilities myteam.myCapability --capability-version 1`
+  instead of `smartthings capabilities myteam.myCapability 1`. Note that the version is always one,
+  so this flag is not necessary at this time.
+* We now use ES modules.
+* We have migrated from oclif to yargs.
+
 ## 1.10.5
 
 ### Patch Changes

README.md

@@ -2,10 +2,12 @@
 
 ## Overview
 
-The default CLI configuration can be overridden by creating a YAML file called `config.yaml` in the
-following location:
+The default CLI configuration can be overridden by creating a YAML file called `config.yaml`. The
+location of this file varies by operating system. The easiest way to find it is to run `smartthings config`
+on your machine and the full filename will be listed.
 
-* `$HOME/.config/@smartthings/cli` on MacOS or Linux
+* `$HOME$/Library/Preferences/@smartthings/cli` on MacOS
+* `$HOME/.config/@smartthings/cli` on Linux
 * `%LOCALAPPDATA%\@smartthings\cli` on Windows
 
 ## Profiles