Gel Project Init Configuration Directory Incorrect

[chuckyQ]

• Gel Version: 7.1+ec15259
• Gel CLI Version: Gel CLI 7.10.2+e00c46c
• OS Version: Windows 11

Steps to Reproduce:

1. Create an empty directory (some-sample-dir)
2. Run gel init in this directory
3. Create a main.go file and add the sample code found on the Golang client library here
4. Run go mod init mymod
5. Run go get github.com/geldata/gel-go
6. Run go run main.go
7. An error will show in the console stating Found 'gel.toml' but the project is not initialized. Run 'gel project init'
8. Run go mod vendor
9. Add the following fmt.Println in the file connutils.go found in geldata/gel-go/internal

	if !exists(stashDir) {
		fmt.Println(stashDir) # Add this
		return errors.New("Found `gel.toml` " +
			"but the project is not initialized. Run `gel project init`.")
	}

10. Run go run main.go

On my machine, I have the following output

C:\Users\Charles\AppData\Local\EdgeDB\config\projects\some-sample-dir-ca0e140e388a02df16b4c64518652ed2f59648e5

I found the folder in the projects directory to have the path of

C:\Users\Charles\AppData\Local\EdgeDB\config\projects\some-sample-dir-99fb64a9fe6875f3a7a40a20ec17ca86f7bb6f87

These added values to the folder (I am guessing some type of hash) are not evaluating the input data in the same way and it is causing the program to fail.

When I manually fix the project folder name in my C:\Users\Charles\AppData\Local\EdgeDB\config\projects with the value shown in the previous fmt.Println statement, the program will run.

After fixing the path, there are more issues connecting to the gel instance through the command line, but I want to focus on this bug first.