Allow use of public_suffix 5

[dentarg]

Changes in public_suffix looks fine to me, no breaking API changes what I can see:

• https://github.com/weppos/publicsuffix-ruby/blob/v5.0.0/CHANGELOG.md#500
• weppos/publicsuffix-ruby@v4.0.7...v5.0.0

Addressable 2.8.1 was just released to allow use of public_suffix 5.x:
https://github.com/sporkmonger/addressable/blob/addressable-2.8.1/CHANGELOG.md#addressable-281

[dentarg]

Hmm, maybe this part needs some tweaking after sporkmonger/addressable#459

twingly-url/lib/twingly/url.rb

Lines 94 to 104 in 767807a

	# Workaround for the following bug in addressable:
	# https://github.com/sporkmonger/addressable/issues/224
	def try_addressable_normalize(addressable_uri)
	addressable_uri.normalize
	rescue ArgumentError => error
	if error.message.include?("invalid byte sequence in UTF-8")
	raise Twingly::URL::Error::ParseError
	end
	raise
	end

Haven't looked into it, I'll leave that to the real maintainers :-)

[Pontus4]

Hmm, maybe this part needs some tweaking after sporkmonger/addressable#459

twingly-url/lib/twingly/url.rb

Lines 94 to 104 in 767807a

	# Workaround for the following bug in addressable:
	# https://github.com/sporkmonger/addressable/issues/224
	def try_addressable_normalize(addressable_uri)
	addressable_uri.normalize
	rescue ArgumentError => error
	if error.message.include?("invalid byte sequence in UTF-8")
	raise Twingly::URL::Error::ParseError
	end
	raise
	end

Maybe this method isn't needed anymore after the updated requirements in 5ae3a68, but as I understand it sporkmonger/addressable#224 isn't completely solved yet. We don't have any URLs in the specs that fails on the normalize step, but that doesn't say that it isn't possible :)

[Pontus4]

🎉