feat(studio): functions management api - attaching functions folder

[kallebysantos]

What kind of change does this PR introduce?

Feature

What is the new behaviour?

Its allows Edge Functions Management API to use folder introspection and serve function metadata.
ref: supabase/supabase#40690, internal RFC

Additional context

screenshots

---

I'm keeping it very simple for now.
Please let me know if a more complex volume binding like this one is needed

cli/internal/functions/serve/serve.go

Lines 253 to 270 in cd22bfe

	binds := []string{}
	for slug, fc := range functionsConfig {
	if !fc.Enabled {
	fmt.Fprintln(os.Stderr, "Skipped serving Function:", slug)
	delete(functionsConfig, slug)
	continue
	}
	modules, err := deploy.GetBindMounts(cwd, utils.FunctionsDir, "", fc.Entrypoint, fc.ImportMap, fsys)
	if err != nil {
	return nil, "", err
	}
	binds = append(binds, modules...)
	fc.ImportMap = utils.ToDockerPath(fc.ImportMap)
	fc.Entrypoint = utils.ToDockerPath(fc.Entrypoint)
	functionsConfig[slug] = fc
	for i, val := range fc.StaticFiles {
	fc.StaticFiles[i] = utils.ToDockerPath(val)
	}

cc @sweatybridge

[sweatybridge]

Let's try to use the binds directories returned from populatePerFunctionConfigs instead. It handles relative imports from ../../../parent.ts for eg.

.
+-- parent/index.ts
+-- supabase
|   +-- functions/slug/index.ts
|   +-- config.toml

Could you also double check that such functions work in the local studio UI?

[kallebysantos]

Hey Qiao! I was able to get the volume binds 💚
But currently, the studio is strict to only look functions in ./**/index.ts way — I didn't happen to think of that other possibility at the time 😅

Since you mentioned this behaviour,
it totally makes sense to add SUPABASE_INTERNAL_FUNCTIONS_CONFIG support for Studio, and I should probably do it in near future 🥹

For now, I think that its ok to only show what's inside supabase/functions folder.
Thx a lot for pointing it 💚