Refactored url-info library to make it less confusing

[begedin]

• Asana task: Refactor url-info library

Self explanatory.

[venkatd]

Looks good. Take a look at the comments for suggestions.

[begedin]

@venkatd: If I'm moving it into external files, then I think it might be a good idea to restructure it a bit.

• urlInfo library calls extractSubdomain (since we don't need the base url here
• extractSubdomain calls extractBaseUrl as an internal step

The only question is, do I extract the two methods into separate file (named after the method), or in a utils/url file, where both methods are exported individually (instead of using a default)?

I'm slightly leaning towards the second option (might be slightly easier to manage), but both could be argued for.

[venkatd]

I like the second option too.

[begedin]

@venkatd I did the extraction to a "url-utils" library.

I decided to keep the mapping method inside url-info, since that part of the behavior is specific to that library and not something we should generally apply. I also renamed the two methods to something more descriptive, to avoid confusion.

Finally, I added a bunch of unit tests for both libraries. I don't think it's worth it to start adding integration tests, since we don't know what the interface is going to be yet, but I should have written some unit tests sooner.

[venkatd]

Looks great. Some minor corrections.

[begedin]

Made the changes, so I'm merging now.