Feathers authentication 1.0 compatible client

[ekryski]

Summary

This makes the client compatible with feathers-authentication v1. Notable changes:

• When calling .authenticate() you pass strategy instead of type. The strategy must match a registered passport strategy that was registered server side.
• Move to supporting accessToken instead of token
• The user is not longer automatically returned. Left up to the developer to fetch
• unauthorized and authenticated events have been removed in the socket auth flow in favour of using the callback mechanism.
• client will automatically try and authenticate if an accessToken exists in localstorage

Tasks Remaining

• Get tests passing
• Update docs
• Migration guide
• Socket auto-authenticate on transport upgrade
• Socket auto-authenticate on re-connect

Other Information

Related to feathersjs-ecosystem/authentication#336

[ekryski]

@marshallswain this is ready for release I think. I was thinking we can add the socket upgrade stuff as a 1.1 release.