Meraki-cli

New Features

- **Native Upgrading**
- Meraki-CLI now has a native upgrade capability with the `meraki upgrade` command path. The help page can be viewed by issuing `meraki upgrade` or `meraki upgrade -h`. There are 4 different options for performing upgrades:
- `--upgrade-all`: Upgrade Meraki-CLI and the Meraki Dashboard API Python SDK package, dependencies will be left alone unless required
- `--upgrade-meraki-cli`: Upgrade only the Meraki-CLI package, dependencies will be left alone unless required
- `--upgrade-meraki-sdk`: Upgrade only the Meraki Dashboard API Python SDK package, others will be left alone unless required
- `--upgrade-all-eager`: Upgrade Meraki-CLI and all its dependencies in an eager fashion
- The feature leverages the PIP utility to perform upgrades of the packages but makes the operation easier for the user by exposing it via the native application

Bug Fixes

- **User-Agent Reporting**
- All HTTP interactions from Meraki-CLI with the Dashboard will now include a User-Agent value in compliance with [Meraki's Ecosystem partner requirements](https://github.com/meraki/dashboard-api-python#note-for-application-developers-and-ecosystem-partners). This is accomplished via a named argument to `meraki.DashboardAPI()` instead of the config file mentioned in the document, but the effect is the same. Unit testing has also been added to make sure the User-Agent string is functional in the REST calls.

- **Version Documentation Testing**
- The Meraki-CLI version is documented in 3 places:
1. The `meraki_cli/__version__.py` file
2. The `README.md` file
3. This file (`CHANGELOG.md`)
- In the past these documentation files have been forgotten when updating the program. Testing has been implemented to make sure these files get updated when a new version is published.

New Features

- **Tab Autocompletion on Linux and MacOS**
- Meraki-CLI now supports tab autocompletion of all commands, switches, and arguments on Linux, MacOS, and limited support on Windows 10. Enablement of autocompletion requires a few steps after upgrade/installation of the Meraki-CLI package. Steps can be found in the [Tab Autocompletion](https://github.com/PackeTsar/meraki-cli/#tab-autocompletion) section of the README.

Bug Fixes

- **Object filtering using inconsistent object keys (10)**
- ISSUE: Some Meraki API endpoints return inconsistent keys in their data. An example of this is the `switch getDeviceSwitchPortsStatuses` command/function which will return lldp keys and values for a port only when data exists to populate the value. Filtering on these inconsistent keys was impossible. The `_object_filter()` function would raise an exception and stop execution if this was encountered. Much more information can be found in Issue 10 where this problem is described in detail.
- FIXES: The `_object_filter()` function has been extended to better handle inconsistent keys. It is also now being tested to filter complex fields.

Misc
- **Python 3.10 Support**
- Full testing against Python 3.10 versions has been added.

- **Python Version in `-v` switch**
- The `meraki -v` command will now include the current Python interpreter version.

- **Local version testing with Tox**
- Config files and instructions have been added to streamline testing against multiple Python versions locally.

Bug Fixes

- **Exception logging**
- ISSUE: Some logging testing was malfunctioning but was not throwing errors until tested in 3.10.
- FIXES: The logging has been fixed to meet the test criteria.

Bug Fixes

- **Positional arguments were not being parsed as JSON**
- ISSUE: Positional arguments which had annotated types of list or dict would be be parsed as JSON. See 9. For example `createNetworkSwitchStack` used with `--serials '["1111-1111-1111", "2222-2222-2222"]'` would not interpret the JSON data into a Python list before passing it to the method. This could be worked around by using `--serials 1111-1111-1111 --serials 2222-2222-2222`, but having JSON decoding would be nice.
- FIXES: Added tests to detect this issue and heavily modified `_get_method_params()` to parse as JSON only when the proper annotations existed in the method params.