Ensure current() method respects 'absolute' option

[bakerkretzmar]

This PR addresses #329 and #348 by ensuring that the .current() method will respect Ziggy's absolute option. What this means is that now, if you set absolute to false, .current() will only consider the pathname when matching the current window URL.

This is a pretty inelegant solution to that problem but it's technically breaking so I want to make it now. I do want to eventually add a flag to .current() itself to accomplish this, or find a better way, but we can add that later in a minor release.

Before:

// APP_URL is https://tighten.co

// On URL https://ozzie.tighten.co/projects
route(undefined, undefined, false).current(); // undefined
route(undefined, undefined, false).current('projects.index'); // false

// On URL https://loosen.com/projects
route(undefined, undefined, false).current(); // undefined
route(undefined, undefined, false).current('projects.index'); // false

After:

// APP_URL is https://tighten.co

// On URL https://ozzie.tighten.co/projects
// Subdomain is ignored because absolute = false
route(undefined, undefined, false).current(); // 'projects.index'
route(undefined, undefined, false).current('projects.index'); // true

// On URL https://loosen.com/projects
// The whole domain is actually ignored, it could be anything, or even missing entirely
route(undefined, undefined, false).current(); // 'projects.index'
route(undefined, undefined, false).current('projects.index'); // true