This script looks better placed in python_modules/automation since it's generating some persisted artifacts (the query snapshots) - it should probably be invoked as dagster-graphql-client.

Might make sense to split the logic you have in check_python_client_queries_in_backcompat_directory. It's pretty hard to grok what's happening. There's two things you are doing:

1. Checking if all queries are present
2. Rehydrating the queries

1 and 2 should be separate methods (i.e. separate click commands), instead of gating by boolean. Just seems cleaner to separate these ideas.

Then, we can just invoke them separately. The bk check would do something like dagster-graphql-client query check and if that fails, then the user should dagster-graphql-client query snapshot to rehydrate the
client_backcompat/ queries