feat(functions) update functions template to match new 'server' style

[kallebysantos]

What kind of change does this PR introduce?

Feature

What is the new behavior?

Apply withSupabase helper from @supabase/server

Additional context

A new optional flag --auth was introduced for the functions new command, chose between the auth access template:

• always No credentials required - Open endpoints, wrappers that handle their own auth
• apikey Valid publishable key or secret key - Use respectively for Client-facing, key-validated endpoints or Server-to-server, internal calls
• user User JWT required - Authenticated user endpoints

Current default --auth apikey

--
Towards FUNC-563

[coveralls]

Coverage Report for CI Build 25128379328

Coverage decreased (-0.04%) to 63.715%

Details

• Coverage decreased (-0.04%) from the base build.
• Patch coverage: 5 uncovered changes across 2 files (19 of 24 lines covered, 79.17%).
• 11 coverage regressions across 4 files.

Uncovered Changes

File	Changed	Covered	%
cmd/functions.go	4	1	25.0%
internal/functions/new/new.go	20	18	90.0%

Coverage Regressions

11 previously-covered lines in 4 files lost coverage.

File	Lines Losing Coverage	Coverage
internal/utils/git.go	5	57.14%
internal/debug/postgres.go	3	66.09%
internal/storage/rm/rm.go	2	80.61%
cmd/functions.go	1	45.92%

---

Coverage Stats

Relevant Lines:	15629
Covered Lines:	9958
Line Coverage:	63.71%
Coverage Strength:	7.03 hits per line

---

💛 - Coveralls

[kallebysantos]

WIP: Do not merge until @supabase/server be announced

[avallete]

A few comments. Otherwise LGTM.

[avallete]

question

Should this be pinned to a major version like for functions-js ?

[tomaspozo]

also maybe we use always jsr: or npm: for all imports on these sample codes...

[kallebysantos]

It would be nice, but I remember a previous issue where was decided to use the deno.json file to import packages.

Not sure if I should just add it as in-line import directly from jsr: same way I keep for dashboard templates

[avallete]

I don't get it 🤔

The current @supabase/functions-js is in deno.json but still import from jsr: with a fixed major version. Not a deno expert though but it seems that we could do the both that way ?

Also, from our docs, the deno.json approach is the preferred one: https://supabase.com/docs/guides/functions/dependencies#using-denojson-recommended

Which make sense, it's much easier and reliable for us to bundle the functions locally with that approach (I think that's the reason why we made this the recommended way).