Version incompatibility for Azure Functions Core Tools blocks execution of `swa start`

**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`

**Describe the bug**
Working in ubuntu on the latest version of node and the swa cli, adding managed apis causes the cli to no longer work in terms of starting the app because of a version incompatability being registered between node and the azure functions core tools.

> ✖ Found Azure Functions Core Tools v4 which is incompatible with your current Node.js v24.5.0.
> ✖ See https://aka.ms/functions-node-versions for more information.

**To Reproduce**
Steps to reproduce the behavior:

1. Install node
```
> node --version
v24.5.0
```
2. Install swa
```
> swa --version
2.0.6
```
3. In an swa project, create a dotnet8 isolated function runtime (could work with others but this is what I used)
4. Make sure to add your ap directory to your swa cli config
5. Run `swa start` triggering core tools grab and then error due to version incompatability```
>swa start
✖ Found Azure Functions Core Tools v4 which is incompatible with your current Node.js v24.5.0.
✖ See https://aka.ms/functions-node-versions for more information.
```

**Expected behavior**
`swa start` should work OR I should be able to disable parts of the project from being booted up to get around these sorts of errors.

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

- Ubuntu 24.04

まず、マネージド API、Node.js v24.5.0、SWA CLI 2.0.6、および .NET 8 の分離された関数ランタイムを使用する SWA プロジェクトで、`swa start` を使って問題を再現します。マネージド API の構成と Azure Functions Core Tools の起動経路を追跡します。CLI でこの構成を起動できるか、失敗しているプロジェクトコンポーネントを無効にする方法が文書化されて提供されれば完了です。

索引モデルが issue の本文から書いたものです。