Add support for dotnetisolated v10

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).

2.0.9

**Describe the bug**
A clear and concise description of what the bug is.

My function is build with net10, but went I set the api-version to 10.0 I get the following error

```
13-Jul-2026 18:46:46 | - Preparing deployment. Please wait...
-- | --
13-Jul-2026 18:46:48 | ✖ Cannot deploy to the function app because Function language info isn't provided, use flags "--api-language" and "--api-version" or add a "platform.apiRuntime" property to your staticwebapp.config.json file, or create one in ./src. Please consult the documentation for more information about staticwebapp.config.json: https://learn.microsoft.com/azure/static-web-apps/build-configuration?tabs=github-actions#skip-building-the-api
13-Jul-2026 18:46:48 | ✖ Deployment failed with exit code 1
13-Jul-2026 18:46:48 | ✖ The deployment binary exited with code 1.
13-Jul-2026 18:46:48 | ✖ If you are running in a minimal container image, ensure native dependencies are installed.
13-Jul-2026 18:46:48 | ✖ Run ldd /home/bamboo/.swa/deploy/689a6c1fe8fc32f40348cc41223a7e9d83dd43d2/StaticSitesClient to check for missing shared libraries.
```

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

1. Add NET 10 API as publish output (not source code) 'dotnet publish api.csproj -o ./api'
2. Type in command 'npx @azure/static-web-apps-cli deploy ./src --env production --api-location ./api --api-language "dotnetisolated" --api-version "10.0" ...'

You get the error above

It should not give errors, as .net 10 was released last November.
If I change the version to 9.0, the deployment works fine, so probably api version is irrelevant?

The fix trivial: change the constants file
https://github.com/Azure/static-web-apps-cli/blob/main/src/core/constants.ts#L307

Commencez dans src/core/constants.ts, vers la ligne 307, où sont définies les valeurs de langue et de version d’API prises en charge. Reproduisez la commande de déploiement de l’issue ou exécutez les tests CLI concernés, puis vérifiez qu’une sortie de publication dotnetisolated v10 est acceptée sans l’erreur language-info signalée.

Rédigé par le modèle d'indexation à partir du texte de l'issue.