🔥 simplify auth plugin further

Remove all references to "email" since we don't actually store the email any more, only the opcode. We were duplicating the opcode as the email recently, might as well remove it to avoid confusion

• remove the methods to return the server tokens, we currently use the opcode as the token directly
• raise errors if we try to set the opcode through the plugin since we are doing so directly from the javascript in the KVStore

This is part of the workaround for
e-mission/e-mission-docs#930

:bug: Fix regression in iOS caused by calling removed function

What's Changed

• 🐛 Remove call to obsolete function by @shankari in #47

Full Changelog: v1.7.0...v1.7.1

Support simplifying auth to only support tokens

What's Changed

• 🔥 Only support the token auth method by @shankari in #46

This is a fairly complex change that involves removing large amounts of obsolete code and the related dependencies
This is the first task in e-mission/e-mission-docs#838 (comment)

Full Changelog: v1.6.5...v1.7.0

⬆️ Upgrade to the latest version of everything 🎉

• Upgrade to the most recent versions of all libraries
• Switch from <framework src="XXX" type="podspec" spec="~> YYY"/> to the <podspec> tag
• Ensure that the podspec tag is formatted correctly
• Switch to @import to use modules instead of using #include
• Change Google auth on iOS to handle function deprecation
• Update README to indicate current state of the OpenIDAuth support

Add null check since we now have callbacks without data

Related commit: e-mission/e-mission-data-collection@a726584
Related release: https://github.com/e-mission/e-mission-data-collection/releases/tag/v1.6.0

Fix prompted auth storage

It turns out that the prompted auth storage locations for iOS (a lot) and android (a little) are not that reliable. We have had multiple iOS users and at least one android user have their stored token deleted.

One of the iOS users said that she had problems with her phone so she had reset to defaults. Maybe that is the problem?

We have seen this for only one android user so far, but it appears to happen on android as well. Storing this in the database instead since that appears to be more reliable.

This fixes
e-mission/e-mission-docs#579

Upgrade to [email protected] and [email protected]

• Fix package.json and hook
• Migrate to androidX
• bump up version number
• add preference for Google Play Services

Upgrade to lastest version of auth libraries

To remove references to UIWebView

Upgrade to cordova-android 7+

Merge pull request #37 from shankari/add_generated_token

Change the class import script to work with the cordova 7+

Add an option to programatically save local tokens

Sometimes, we don't want to prompt the user for a token but generate one in the javascript and store it. The generating is easy enough, but the storage is currently hard since it involves sending a custom URL notification to the plugin.

Instead of fiddling around with weird inapp browser schemes to pass through the URL, let us handle this directly in the plugin since we wrote it ourselves.

• bump up version number