If a session isn't in the DB, don't error when destroying.

When destroying a session, if that session doesn't exist in the database, then Sequelize will return a null from the .find, indicating that the find executed normally, but didn't find anything.

Currently this throws an exception.

We can probably just assume that the session has been destroyed, because it's not in the DB any more, and pretend like the destroy succeeded.