docker-compose.yml is not consistent with aerie-gateway

[parkerabercrombie]

Checked for duplicates

No - I haven't checked

Is this a regression?

No - This is a new bug

Version

3.0.1

Describe the bug

I received an error when attempting to import a plan into Aerie. On further investigation, the docker-compose file sets env var GQL_API_URL (https://github.com/NASA-AMMOS/aerie/blob/develop/deployment/docker-compose.yml#L8) but aerie-gateway expects env var HASURA_API_URL https://github.com/NASA-AMMOS/aerie-gateway/blob/5c616b4eb7e6fec9c42a5e22cfd4a12b4cbc2dd3/src/packages/plan/plan.ts#L37. This results in Aerie incorrectly using a default URL.

Reproduction

N/A

Logs

No response

System Info

Chrome

Severity

Major

[parkerabercrombie]

aerie-gateway also expects the hasura URL var to be only the host, not the /v1/graphql path, which is inconsistent with other services.