test: add confDir test and fix linting in integration spec

[p4rthh]

Description

This PR adds an integration test for the --confDir flag (src/test/confDir.spec.ts).

Changes

• Added src/test/confDir.spec.ts to verify the flag functionality.
• Applied npm run fix to src/test/cli.integration.spec.ts to resolve upstream linter errors (Tabs vs Spaces) as discussed in Discord.

Notes

The cli.integration.spec.ts logic remains unchanged; only formatting was updated to pass the linter.

[viferga]

@p4rthh I just checked the test and the flag --confDir is not being tested. The test should be something like this:

deploy/src/test/cli.integration.spec.ts

Line 53 in b58283b

// --token

The test in general is good, specially the before and after callbacks, but it should pass the --confDir with the proper token to see if it logins accordingly. It's fine to set it up on a empty folder so it does not deploy, but we can verify that is login properly with a config on a different folder.

[viferga]

If you test like you are doing, you skip the whole purpose of testing --confDir like in here:

deploy/src/logs.ts

Line 20 in b58283b

const config = await startup(args['confDir']);

args['confDir'] is what should be tested, not startup, that's why I prefer if we do integration test directly with the flag.

[viferga]

@p4rthh I have done two more changes, I have restored exactly how the TODO comments were before. It's important to be atomic whenever possible and don't change things in a commit that are unrelated, even if it is just spaces and nothing changed.

The other thing I have changed is the writeFileSync, I made it async. I am going to squash the commits into one but you can check the final code to see the differences.

[viferga]

@p4rthh your PR broke the CI in production:
https://github.com/metacall/deploy/actions/runs/20522626563/job/58961039478