fix: fixes specifying / as a path for v2 api functions

[lukasholzer]

🎉 Thanks for submitting a pull request! 🎉

Summary

Fixes https://github.com/netlify/pod-dev-foundations/issues/597

Fixes an issue where specifying the following config did not work:

import type { Context, Config } from '@netlify/functions';

export default (req: Request, context: Context) => {
  return new Response(`Hello World`, { status: 200 });
};

export const config: Config = {
  path: '/', // <-- did not work in the CLI
};

---

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 8183fd0

• Dependency count: 1,386 (no change)
• Package size: 389 MB ⬇️ 0.00% decrease vs. 8183fd0

[lukasholzer]

I've just seen the same issue is in production @Skn0tt do you know where to fix that?

cc @eduardoboucas

[Skn0tt]

I noticed that we were also not matching / on the /* route. The fix in this PR also fixed that, so I added my test onto this PR: cbbb2c2