refactor: replace got with node-fetch on dev-miscellaneous.test.js

[hereje]

Summary

refactor: replace got with node-fetch on dev-miscellaneous.test.js

related to #5695

---

For us to review and ship your PR efficiently, please perform the following steps:

• Open a bug/issue before writing your code 🧑‍💻. This ensures we can discuss the changes and get feedback from everyone that should be involved. If you`re fixing a typo or something that`s on fire 🔥 (e.g. incident related), you can skip this step.
• Read the contribution guidelines 📖. This ensures your code follows our style guide and
  passes our tests.
• Update or add tests (if any source code was changed or added) 🧪
• Update or add documentation (if features were changed or added) 📝
• Make sure the status checks below are successful ✅

A picture of a cute animal (not mandatory, but encouraged)

[github-actions]

📊 Benchmark results

Comparing with 51f1cf6

• Dependency count: 1,359 (no change)
• Package size: 313 MB (no change)
• Number of ts-expect-error directives: 980 (no change)

[github-actions]

📊 Benchmark results

Comparing with 3268f29

• Dependency count: 1,398 (no change)
• Package size: 404 MB (no change)
• Number of ts-expect-error directives: 0 (no change)

[mrstork]

For a while there looked to be several unrelated errors preventing this from getting merged, but most of those flaky tests look to have been resolved in main so I took a stab at merging the latest into this branch. Unfortunately though, the most recent run does look to have a genuine failure related to the code this function is testing, though it very well might be specific to windows + node 20.

FAIL  tests/integration/commands/dev/dev-miscellaneous.test.js > commands/dev-miscellaneous > should detect content changes in edge functions
AssertionError: expected 'There was an error with an Edge Funct…' to deeply equal 'Hello builder'

- Expected
+ Received

- Hello builder
+ There was an error with an Edge Function. Please check the terminal for more details.

When I have some time again, I will try to spin this up on a local windows instance to see if I can uncover why the edge function might be returning an error in this case.

[mrstork]

I played around with removing this delay and was able to uncover something potentially useful, but did not ultimately uncover the root of the problem. With no pause, we will see different results:

mac + node v20.12.2 + got -> 'Hello world'
windows + node v20.12.2 + got -> 'Hello world'

mac + node v20.12.2 + fetch -> 'Hello world'
windows + node v20.12.2 + fetch -> ECONNREFUSED

I also found this potentially related node 18 issue node-fetch/node-fetch#1624. Even though the test is failing on a different version of node, I tried changing the url in the test from localhost to 127.0.0.1 but saw no change in behaviour.

It doesn't actually solve the underlying issue, but given the above, increasing this delay up from 500 should get the tests to pass.

[mrstork]

To be clear, the changes in this PR do not introduce an issue (as they are just modifying a test), they simply bring to light an issue that exists somewhere in our codebase. Some interaction between some or all of the following components: edge proxy, fetch, builder (on windows)