Add support of .NET10 isolated model runtime

[Hoodys352]

Context

Describe the context or motivation for this PR. Include links to any related Azure DevOps Work Items or GitHub issues.
📌 How to link to ADO Work Items
#21781

---

Task Name

Name of the updated or newly created pipeline task.

AzureFunctionAppV1
AzureFunctionAppV2

Description

Summarize the changes made in this PR clearly and concisely.

Added DOTNET-ISOLATED|10.0 support

Risk Assessment (Low / Medium / High)

Assess the level of risk and provide reasoning (e.g., scope, impact, backward compatibility).

Low

Change Behind Feature Flag (Yes / No)

Can this change be behine feature flag, if not why?

---

Tech Design / Approach

• Design has been written and reviewed.
• Any architectural decisions, trade-offs, and alternatives are captured.

---

Documentation Changes Required (Yes/No)

Indicate whether related documentation needs to be updated.

• User guides, API specs, system diagrams, or runbooks are updated.

---

Unit Tests Added or Updated (Yes / No)

Indicate whether unit tests were added or modified to reflect these changes.

No

Additional Testing Performed

List all other tests performed (manual or automated, including integration, regression, scenario tests, etc.).

---

Logging Added/Updated (Yes/No)

• Appropriate log statements are added with meaningful messages.
• Logging does not expose sensitive data.
• Log levels are used correctly (e.g., info, warn, error).

---

Telemetry Added/Updated (Yes/No)

• Custom telemetry (e.g., counters, timers, error tracking) is added as needed.
• Events are tagged with proper metadata for filtering and analysis.
• Telemetry is validated in staging or test environments.

---

Rollback Scenario and Process (Yes/No)

• Rollback plan is documented.

---

Dependency Impact Assessed and Regression Tested (Yes/No)

• All impacted internal modules, APIs, services, and third-party libraries are analyzed.
• Results are reviewed and confirmed to not break existing functionality.

---

Checklist

• Related issue linked (if applicable)
• Task version was bumped — see versioning guide
• Verified the task behaves as expected

[Hoodys352]

@microsoft-github-policy-service agree

[Hoodys352]

/azp run

[azure-pipelines]

Commenter does not have sufficient privileges for PR 21782 in repo microsoft/azure-pipelines-tasks

[FinVamp1]

@Hoodys352 thanks for the contribution, I updated your PR with the other stacks also, PLease review and let me know if you have any concerns. If you don't then I will approve and merge?

[FinVamp1]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[Hoodys352]

@Hoodys352 thanks for the contribution, I updated your PR with the other stacks also, PLease review and let me know if you have any concerns. If you don't then I will approve and merge?

@FinVamp1 Hi, no problem, thanks for extending this PR!

[FinVamp1]

Approved

[Hoodys352]

@FinVamp1 is there anything else I need to do? It's my first PR

[patelchandni]

Why task.loc.json does not have rest of the language versions like task.json? Same question for V1 task.loc.json.

[FinVamp1]

I think the build step will fix this but that's something I will verify today.

[Hoodys352]

@FinVamp1 any news?