[TRI-699] The CLI init command fails on Windows because of file:// paths

[matt-aitken]

Steps to reproduce

Running the init command on Windows results in this:

"√ Successfully added dependencies to package.json: @trigger.dev/sdk@2.0.0-next.18, @trigger.dev/nextjs@1.0.0-next.8
✅ Added TRIGGER_API_KEY=*** to .env.local
✅ Added TRIGGER_API_URL=https://cloud.trigger.dev/ to .env.local
Aborting installation...
Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file and data URLs are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'd:'"

_TRI-699

[ericallam]

/bounty $50

[algora-pbc]

💎 $50 bounty created by ericallam
🙋 If you start working on this, comment /attempt #190 to notify everyone
👉 To claim this bounty, submit a pull request that includes the text /claim #190 somewhere in its body
📝 Before proceeding, please make sure you can receive payouts in your country
💵 Payment arrives in your account 2-5 days after the bounty is rewarded
💯 You keep 100% of the bounty award
🙏 Thank you for contributing to triggerdotdev/trigger.dev!

Attempt	Started	Solution
🟢 @dylanrod21	Jul 19, 2023	#194

[dylanrod21]

/attempt #190

[dylanrod21]

I was able to resolve the issue, I just tested its working locally, ill put together a pull request now for review.

[algora-pbc]

💡 @dylanrod21 submitted a pull request that claims the bounty. You can visit your org dashboard to reward.

[algora-pbc]

🎉🎈 @dylanrod21 has been awarded $50! 🎈🎊