SG-44731 Fetch git-lfs content during Azure Pipelines checkout

[julien-lang]

Problem

Azure Pipelines does not retrieve Git LFS content by default on a checkout, even for repos that have LFS-tracked files. Jobs that read those files (e.g. Sphinx doc generation, App Store release/test jobs) could silently work with pointer text instead of real content.

Fix

Add an explicit checkout: self step with lfs: true before any other step, in the three pipeline templates that checkout the repository being built: code-style-validation.yml, release.yml, run-tests-with.yml.

Testing

• Reviewed the diff against origin/master: only these 3 files change, each gets the same checkout: self / lfs: true step, matching the existing indentation style of that file.

[Copilot]

Pull request overview

This PR updates internal Azure Pipelines templates to explicitly enable Git LFS during repository checkout so pipeline jobs operate on real LFS content instead of pointer files.

Changes:

• Add an explicit checkout: self step with lfs: true near the start of job steps in the affected templates.
• Document why the explicit checkout is required (Azure Pipelines default checkout doesn’t fetch LFS objects).

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
internal/run-tests-with.yml	Adds an explicit checkout: self step with lfs: true before subsequent test steps.
internal/release.yml	Adds an explicit checkout: self step with lfs: true before release steps.
internal/code-style-validation.yml	Adds an explicit checkout: self step with lfs: true for the documentation-build job.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[julien-lang]

I could but... code_style_validation does not need to LFS checkout so ...

Still would not hurt. But then I should do for every job and be consistent