Remove broken Navitia endpoints

[ialokim]

Unfortunately, Navitia removed several regions from their servers. We should remove them from Transportr too.

1. check all endpoints that are currently served by Navitia (inheriting the NavitiaProvider.java in PTE)
2. list them here in the issue
3. remove the dis-functional ones in a PR

[ialokim]

Here's a list of all providers based on Navitia from PTE, marked with if they are still served by navitia.io. The list was recompiled from the PTE sources and compared to the response returned by https://api.navitia.io/v1/coverage (valid API token needed).

AbstractNavitiaProvider	coverage	still working
AustraliaProvider	au	✅
BrFloripaProvider	-²	❌
BrazilProvider	br	❌
BritishColumbiaProvider	ca-bc	❌
CaliforniaProvider	us-ca	❌
CostaRicaProvider	-¹	❌
CzechRepublicProvider	cz	❌
FinlandProvider	fi	❌
FranceNorthEastProvider	fr-ne	✅
FranceNorthWestProvider	fr-nw	✅
FranceSouthEastProvider	fr-se	✅
FranceSouthWestProvider	fr-sw	✅
GhanaProvider	gh	❌
HungaryProvider	hu	❌
IsraelProvider	il	❌
ItalyProvider	it	✅
MassachusettsProvider	us-ma	❌
NewyorkProvider	us-ny	❌
NicaraguaProvider	ni	❌
NzProvider	nz	❌
OntarioProvider	ca-on	❌
OregonProvider	us-or	❌
ParisProvider	fr-idf	✅
PlNavitiaProvider	pl	❌
PortugalProvider	pt	❌
QuebecProvider	ca-qc	❌
SpainProvider	es	✅
WashingtonDCProvider	us-dc	❌

¹= The Costa Rica region was apparently served by http://98.158.179.5:9191/ which is not reachable anymore either

²= br-floripa was served by https://api.transportr.app/floripa/v1/ which shows 500 Internal Server Error

As you can see, most of the listed providers are unfortunately not served anymore by Navitia and should be removed from Transportr in the next version.

[ialokim]

br-floripa was served by https://api.transportr.app/floripa/v1/ which shows 500 Internal Server Error, should we remove it from Transportr @grote ?

[grote]

Yes please.

[ialokim]

Fixed with #884