fix(misc): use string type for fetchDepth in azure-pipelines.yml

[fALKENdk]

The Azure Pipelines schema requires fetchDepth to be a string, but the generator was outputting a number.
This fix changes the value to a string to match the official schema specification.

Current Behavior

The generator creates azure-pipelines.yml with fetchDepth: 0 (number), which causes YAML schema validation error because the Azure Pipelines schema expects fetchDepth to be a string.

According to the Azure Pipelines schema, fetchDepth is defined as:

"fetchDepth": {
    "description": "Depth of Git graph to fetch",
    "$ref": "#/definitions/string"
}

Expected Behavior

The generator should output fetchDepth: '0' (string) to match the schema specification and prevent validation errors.

[netlify]

👷 Deploy request for nx-docs pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	4b6c9f3

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
nx-dev	Ready	Preview	Dec 15, 2025 0:09am

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 4b6c9f3

Command	Status	Duration	Result
nx affected --targets=lint,test,test-kt,build,e...	✅ Succeeded	37m 43s	View ↗
nx run-many -t check-imports check-lock-files c...	✅ Succeeded	2m 25s	View ↗
nx-cloud record -- nx-cloud conformance:check	✅ Succeeded	11s	View ↗
nx-cloud record -- nx format:check	✅ Succeeded	2s	View ↗
nx-cloud record -- nx sync:check	✅ Succeeded	<1s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-12-15 14:26:13 UTC