Update PublicSuffix and Addressable

[roback]

Unfortunately it doesn't look like this fixes any of our issues, but since it made the profiling run a bit faster (and the fact that the tests didn't break) I made a PR of this anyway.

Profiling "total run time" went from 1.6663s to 1.4801s.

Some related links:

• Keep the index continuously updated instead of explicitly fully reindexing weppos/publicsuffix-ruby#130
• Switch List implementation to use Hash-based lookup weppos/publicsuffix-ruby#133
• Allow public_suffix 3 sporkmonger/addressable#267

[walro]

We could take the opportunity and think about: #104 (comment)

My experience that going from loose requirements to strict ones made it a bit cumbersome for Bundler to figure out how to update. I would usually end up with twingly-url not being updated at all (unless I danced a bit). Not sure what I proposed, allowing patch versions, would be a silver bullet but it would likely help in some cases at least.

[roback]

Just a note: We need at least Addressable 2.5.2, since that is the only version is compatible with public suffix 3.x: https://github.com/sporkmonger/addressable/blob/master/CHANGELOG.md#addressable-252

[walro]

We could allow for something like: public_suffix >= 2, < 4 and something similar for addressable and let bundler figure out the rest. I am not really sure about how we properly test all combinations though.

[roback]

I am not really sure about how we properly test all combinations though.

Looks like Travis already thought of that: https://docs.travis-ci.com/user/languages/ruby/#Testing-against-multiple-versions-of-dependencies, though we have to create the gemfiles manually.

[texpert]

Pleading for a new release with this PR merged, because the google-api-client gem is long time requiring the 'addressable', '~> 2.5', '>= 2.5.1'

[dentarg]

Let's get this merged and released and then loosen up the dependencies and test with multiple gemfiles.

[dentarg]

@texpert done! see https://rubygems.org/gems/twingly-url/versions/5.1.1

[texpert]

Awesome, @dentarg , thanks a lot!!