Feature Request: Allow Override of Container Image Name for SurrealDB In Memory Container#60

I’m using surql-gen (v2.6.0) in an environment where pulling images directly from Docker Hub is blocked due to a VPN/proxy. I have a SurrealDB image available in our Artifactory, but the tool tries to pull the latest image from Docker Hub. ### Feature Request: It would be really useful to have an option to override the default SurrealDB container image name, like how Helm charts allow for container overrides. This would let users specify a custom image from an internal registry (e.g., Artifactory), making the tool more flexible in different network setups where Docker Hub isn’t accessible, and images need to come from an internal registry. ### Proposed Solution: Add a config option in surql-gen to let users pull `surrealdb:latest` from an internal registry. Example usage: ```bash npx surql-gen -f schema.surql -o ./output --no-generate-client --container-registry myregistry.com/surrealdb/surrealdb:latest ``` That would update pass in the registry URL [here](https://github.com/sebastianwessel/surrealdb-client-generator/blob/main/src/database/db.ts#L19). Thanks for considering this! The tool has been super helpful, and this feature would make it even better for different environments.