No errors at deployment when using runtime v4 with managed functions

Before filing this issue, please ensure you're using the latest CLI by running `swa --version` and comparing to the latest version on [npm](https://www.npmjs.com/package/@azure/static-web-apps-cli).

**Are you accessing the CLI from the default port `:4280` ?**

- [ ] No, I am using a different port number (`--port`) and accessing the CLI from that port
- [x] Yes, I am accessing the CLI from port `:4280`

> Make sure you are accessing the URL printed in the console when running `swa start`!

**ℹ️ NOTE: Make sure to enable debug logs when running any `swa` commands using `--verbose=silly`**

**Describe the bug**
When using runtime v4 with a JS/TS managed functions API, no error is shown during deployment with SWA CLI (shows success message) but no functions are actually deployed.

**Note:** Now, I know that v4 runtime is currently not supported, but I didn't at the time and was caught trying to understand why my functions were missing for hours.

**To Reproduce**
1. Create a SWA project with a function API using JS v4 runtime
2. Run SWA deploy

**Expected behavior**
A warning or error message should be displayed to the user to indicate that runtime v4 is not currently supported.

**Desktop (please complete the following information):**

- OS: MacOS
- Version 14.4

Beginne damit, die dokumentierte Reproduktion von `swa deploy` mit einer von JavaScript oder TypeScript verwalteten Functions-API unter Verwendung von runtime v4 auszuführen, und untersuche die in der Issue angeforderte ausführliche Ausgabe. Verfolge, wie die Bereitstellung mit der nicht unterstützten runtime umgeht; abgeschlossen ist die Aufgabe, wenn die Bereitstellung eine klare Warnung oder einen Fehler meldet, anstatt Erfolg zu melden, wenn keine Functions bereitgestellt werden.

Vom Indexierungsmodell aus dem Issue-Text verfasst.