…ease

…ues (#5867)

When function deployment fails due to insufficient quota on Cloud Run, the error message is difficult to understand:

```
i  functions: creating Node.js 18 function helloWorld(us-east4)...
⚠  functions: HTTP Error: 400, Could not create Cloud Run service helloworld. spec.template.spec.containers.resources.limits.cpu: Invalid value specified for cpu. For the specified value, maxScale may not exceed 10.
Consider running your workload in a region with greater capacity, decreasing your requested cpu-per-instance, or requesting an increase in quota for this region if you are seeing sustained usage near this limit, see https://cloud.google.com/run/quotas. Your project may gain access to further scaling by adding billing information to your account.
```

Updated error message, which we hope is clearer and actionable:

```
i  functions: creating Node.js 18 (2nd Gen) function helloWorld(us-east4)...
⚠  functions: Your current project quotas don't allow for the current max instances setting of 100. Either reduce this function's maxInstances, or request a quota increase on the underlying Cloud Run service at https://cloud.google.com/run/quotas.
⚠  functions: You can adjust the max instances value in your function's runtime options:
	setGlobalOptions({maxInstances: 10})
```

…debug mode."

This reverts commit cfb94a2.

* Handle Nuxt bundled dependencies
* Add fast dev-mode to Nuxt 2
* Handle ssr true/false in Nuxt apps in a more conventional way
* Import all the integrations, rather than dynamically require
* Leave it to the framework to rewrite as an SPA
* Handle Nuxt3 baseURL
* SPAs for Nuxt3 and Angular now respect baseUrl
* If the Nuxt version couldn't be determined, assume Nuxt v3
* Nuxt used process.cwd in a couple places, guard against this
* Allow for Angular apps leveraging serveOptimizedImages to still be treated as an SPA

Co-authored-by: James Daniels <jamesdaniels@google.com>

* Tweaking some text string formatting as a follow-up to PR 5867.

* Removing stray backtick.

* Platform agnosticizing our usage of 'max instances.'

Co-authored-by: James Daniels <jamesdaniels@google.com>

…ode. (#5878)

Instead of spawning a new process that exposes the debugger endpoint, the Functions Emulator will attempt to explicitly kill the existing process before loading the function with the updated source code.

Possible fix for #5508, #5653.