VRS: fix nearby stations about tripkit HOT 1 CLOSED

I think I finally figured this one out. The following only applies to the https endpoint. However this does not fix the underlying issue where the tx_vrsinfo_ass2_timetable path cannot be used anymore for coord requests.

The iOS app accesses ekapapp.vrsinfo.de instead of android.vrsinfo.de. The app also makes requests to tx_vrsinfo_ass2_timetable, so this endpoint should be still active. The interesting part is that a http request to tx_vrsinfo_ass2_timetable does not work and returns "no valid id" (see original comment). So we have to use https, which brings us to another problem: ERR_BAD_SSL_CLIENT_AUTH_CERT .

https requests to ekapapp.vrsinfo.de require a client certificate. I found the certificate in the latest android app under assets/ekap-android-v2.vrs.de.pfx. But not so fast - the certificate requires a password. Thankfully, de.sidebysite.auskunftlibrary.util.EkapApiService#getSSLContext tells us where exactly we can find it - AndroidManifest.xml. Decoding the manifest using eg. apktool, we can finally extract the passcode, use it to import the cert and use the cert for the https requests and tada 🎉 - the endpoint works!

from tripkit.