Staging deploy of FTL

[alecthomas]

Remaining tasks:

• Authentication plugin system
• Figure out how to distribute ftl-authenticator-tbddev - it is in a private GH repo. (@alecthomas)
• Configure ftl-controller deployment to wait for Istio before starting. Currently it seems to start before Istio's DNS is ready, and it fails to find the PG cluster address. Solution is below.
  error: Streaming RPC failed: failed to connect to host=ftl-psql-cluster-cbhr8-pm96f.cluster-cknqvaeiurv8.us-west-2.rds.amazonaws.com user=adminuser database=tbd: hostname resolving error (lookup ftl-psql-cluster-cbhr8-pm96f.cluster-cknqvaeiurv8.us-west-2.rds.amazonaws.com on 172.20.0.10:53: no such host): /xyz.block.ftl.v1.ControllerService/RegisterRunner
• Export metrics to DD - this is not specific to FTL, it seems no custom metrics are being collected yet. (@alec-brooks)
• Verify logs are being shipped to DD - they are being exported, but they're plaintext not structured JSON
  • Configure JSON logging in ftl-controller and ftl-runner (@alecthomas)
  • Figure out how to configure DD to ingest JSON logs (@alec-brooks)
• Verify traces are being shipped to DD (@alec-brooks)
• Configure DD monitoring once we have metrics. (@alecthomas)

[alecthomas]

This is basically working, thanks to the efforts of @alec-brooks!

We need a few more things to be fully complete, but ftl status is working!