Use current Accounts token location in auth endpoints

- Update the default auth endpoints to store and remove tokens from the
  location expected by the Meteor Accounts package
  - The `accounts-base` package now stores hashed tokens in
    `services.resume.loginTokens.hashedToken`, instead of storing a
    `services.resume.loginTokens.token` unhashed.
- Resolve kahmali#79

CHANGELOG.md

@@ -5,7 +5,8 @@
 #### Warning - Potentially breaking change
 - Restivus used to store the account login token in the user document: `services.resume.loginTokens.token`
 - Restivus now stores the account login token as a hashed token, in the user document: `services.resume.loginTokens.hashedToken`
-- This matches Meteor Accounts package
+- This means that all clients consuming a Restivus API will need to reauthenticate with their 
+  username/email and password after this update, as their existing tokens will be rendered invalid.
 
 #### Changed
 - Update default auth endpoints to match current Accounts token storage (see #79)