Add dynamic key support to schema

[ecooper]

Problem

Schema commands do not support dynamic database keys.

Solution

Add support for dynamic database keys via getSecret() and retryInvalidCredsOnce.

Result

➜  fauna-shell (v3-db-schema) ./src/user-entrypoint.mjs schema pull -d us-std/demo --dir /tmp/schema -p dev                                                                                                                                           ✱
Pull will make the following changes:
overwrite: collections.fsl
overwrite: functions.fsl
overwrite: main.fsl
✔ Accept the changes? yes
➜  fauna-shell (v3-db-schema) ls -la /tmp/schema/                                                                                                                                                                                                     ✱
total 32
drwxr-xr-x  5 ericcooper  wheel   160 Dec  4 12:45 .
drwxrwxrwt  5 root        wheel   160 Dec  4 12:45 ..
-rw-r--r--  1 ericcooper  wheel  2780 Dec  4 12:49 collections.fsl
-rw-r--r--  1 ericcooper  wheel  4539 Dec  4 12:49 functions.fsl
-rw-r--r--  1 ericcooper  wheel   263 Dec  4 12:49 main.fsl
➜  fauna-shell (v3-db-schema)      

Testing

Existing tests should work as-is since this should be a transparent change.

Follow-up

• Consider combining getSecret and retryInvalidCredsOnce into one wrapper.

[echo-bravo-yahoo]

not for this PR, but i think it'd be lower mental overhead to have just one entrypoint (makeFaunaRequest) and pass it opts, argv, and have it choose if it should be retryable or not. exporting multiple entrypoints and expecting consumers to pick correctly is more brittle.