feat: custom claims for setting grpc/server addr in token

[abelanger5]

Description

Removes the requirement of setting HATCHET_CLIENT_HOST_PORT as an environment variable in all of the SDKs. This instead adds custom claims of server_url and grpc_broadcast_address which are used for connections.

Security implications of this approach were considered - one could consider a MITM attack which rewrites the claims to trick the user into sending their token to their server. Our SDKs require TLS to minimize the risk, and if an attacker has constructed a MITM attack during token generation time, they would likely be able to modify the payload which shows the broadcast address to the user anyway. This is also fairly standard practice, i.e. GCP credentials files have a set of auth URIs set:

"auth_uri": "https://accounts.google.com/o/oauth2/auth",
"token_uri": "https://oauth2.googleapis.com/token",
"auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs"

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)

What's Changed

This is backwards-compatible with older tokens.

• SDKs config loaders for all 3 SDKs
• New claims in tokens
• Docs updates to remove requirement of HATCHET_CLIENT_HOST_PORT

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
hatchet	✅ Ready (Inspect)	Visit Preview	Feb 5, 2024 4:27am

[grutt]

need to set this on the go-quickstart docker-compose?