mattdrayer/api-session-check-existing: Skip login if already logged in

@chrisndodge @martynjames -- updated the POST /sessions workflow to skip the login() routine if the user is already logged in -- had to move some code around and added some helper functions along the way.  Let me know what you think.

@fredsmith, FYI on this change -- we'll need to figure out how to work it into the deployment stream -- if we set up a release candidate branch we could cherry-pick the commit into it -- or I suppose we could close this PR and resubmit to the RC, then merge back to master -- however we want to manage the code is fine w/ me
Curious before writing this, did you write a unit test to try to simulate the error we're seeing:

1) call API to login, get token1
2) call API to login again, get token2
3) call API to validate token1 is still valid?

Or at least that is what I think is happening, but I'm trying to work backwards from browser behavior.