tests: fivetran in cloudtests

[nrainer-materialize]

Nightlies: https://buildkite.com/materialize/nightly/builds?branch=nrainer-materialize%3Atests%2Ffivetran-in-cloudtests

[nrainer-materialize]

@ParkMyCar, this is still a draft, but does it make sense so far?

[nrainer-materialize]

"Full testdrive in cloudtests" in nightly reports:

testdrive/fivetran-destination.td:22:1: error: connecting to fivetran destination: transport error: error trying to connect: tcp connect error: Connection refused (os error 111): tcp connect error: Connection refused (os error 111): Connection refused (os error 111)

@ParkMyCar: Can I find somewhere the used URL? I did not spot it in the logs. Though, I assume it is http://fivetran-destination:6874?

@evanharmon: Should testdrive running as standalone binary be able to access http://fivetran-destination:6874? kubectl get services contains the following port mapping:

nrainer@mz-nrainer ~ % kubectl get services | grep fivetran
fivetran-destination    NodePort       10.96.42.20     <none>                                   6874:32041/TCP                                                17m