Drozer

- Parcelable Intent extras should now work as intended (with breaking changes to URI syntax - see `help intents`)
- Users will now be notified if they're running an outdated version of `drozer-agent`
- Minor backwards-compatibility tweaks

- More verbose/thorough error handling
- Update checks for drozer console
- Warn the user if a critically outdated version of drozer-agent is in use
- Official support for Windows (with no tab-complete for the time being)
- Multiple bugfixes, including the revival of the `auxiliary.webcontentresolver` module

Multiple fixes:

- External module repositories (including WithSecure's official one) are now functional
- `scanner.provider.traversal` bug fixes - module should now work as intended
- Byte array extras can now be used in Intents (except when interacting with Services - see https://github.com/WithSecureLabs/drozer/issues/431)
- drozer will no longer crash if the `readline` package is not available (slowly paving the way towards native Windows compatibility)
- `list --unsupported` should now work as intended
- Trying to load a broken module will no longer crash drozer, instead handling the exception gracefully

Fixed some bugs:

* drozer *should* now work on Android 6 (API 23) and below
* fixed the `contributors` module
* modified how drozer handles `--extra intent parcelable <intent object>`
* drozer will now use class `android.content.Intent` method `praseUri(String, int)` to generate the Intent object

Compatibility with Python 3 and modern Java.

With many thanks to:
Ken Gannon NCC Group
William Ben Embarek TDC NET

gave IntentProxyToContentProvider more generic access to unexported content providers