fix: toggle DENO_NO_PACKAGE_JSON conditionally

[nyannyacha]

What kind of change does this PR introduce?

Enhancement

Description

Make CLI conditionally toggle DENO_NO_PACKAGE_JSON based on what files are in each function folder.
This only applies when deploying functions locally/Docker and not using the deploy api.

Related supabase/supabase#38402
Towards FUNC-304

[coveralls]

Pull Request Test Coverage Report for Build 18926015369

Details

• 11 of 16 (68.75%) changed or added relevant lines in 2 files are covered.
• 5 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.01%) to 54.718%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
internal/functions/deploy/deploy.go	4	6	66.67%
internal/functions/deploy/bundle.go	7	10	70.0%

Files with Coverage Reduction	New Missed Lines	%
internal/gen/keys/keys.go	5	12.9%

Totals
Change from base Build 18900105989:	-0.01%
Covered Lines:	6396
Relevant Lines:	11689

---

💛 - Coveralls

[sweatybridge]

I'm not sure if this is the right fix. Based on their example, the error seems to be caused by health function failing to import package.json on Windows.

Most likely we have a bug in path resolution that's preventing package.json at root repo directory from being volume mounted into the edge runtime container.

[nyannyacha]

@sweatybridge Hello qiao 😄

Well.... I think their reproduction code in that link you mentioned is definitely a bug, but I believe what they reproduce is actually a different bug that seems similar to the issue they're having.

Apparently, the cli is parsing the script directly and passing it a list of the paths that should be bound from the host to pass to Docker.
That link is reproducing a bug that occurred there, but the issue that originally caused that issue was that it was automatically reading the package.json and subtly changing the way the Deno codebase resolves modules.

This is a PR for that.