fix(functions): reload kong after edge runtime restart

[okedeji]

What kind of change does this PR introduce?

Bug fix

What is the current behavior?

After supabase functions serve restarts the Edge Runtime container (on file change or initial serve), Kong's DNS cache still points to the old container IP, causing 502 errors on /functions/v1/* endpoints.

closes #4757

What is the new behavior?

Runs kong reload after each Edge Runtime restart to flush DNS cache and resolve the new container IP.

Additional context

The reload is non-disruptive. Kong flushes DNS without dropping in-flight connections. If the reload fails, a warning is printed to stderr and execution continues.

[aantti]

@singh-inder fyi, 🤔

[coveralls]

Pull Request Test Coverage Report for Build 23561179257

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 7 of 7 (100.0%) changed or added relevant lines in 1 file are covered.
• 5 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.005%) to 63.18%

---

Files with Coverage Reduction	New Missed Lines	%
internal/utils/git.go	5	57.14%

Totals
Change from base Build 23561140882:	-0.005%
Covered Lines:	9199
Relevant Lines:	14560

---

💛 - Coveralls