[Python] Remove --locked flag from uv sync in copilot-setup-steps.yml

[Copilot]

CCA invocations fail at the "Install Python dependencies" setup step because uv sync --locked requires a uv.lock file that doesn't exist in python/.

• Removed --locked from the uv sync command in copilot-setup-steps.yml, matching the working python-sdk-tests.yml workflow

Original prompt

---

This section details on the original issue you should resolve

<issue_title>CCA invocations issue an error about Python dependencies</issue_title>
<issue_description>

</issue_description>

<agent_instructions>Determine the root cause and submit a PR to fix it.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes CCA invocations issue an error about Python dependencies #627

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Pull request overview

This PR fixes a failing "Install Python dependencies" step in the Copilot Coding Agent (CCA) setup workflow (copilot-setup-steps.yml). The uv sync --locked flag requires a uv.lock file to exist, but the python/ directory does not contain one, causing the step to error out. The fix removes --locked to match the working python-sdk-tests.yml workflow.

Changes:

• Removed --locked from the uv sync command in copilot-setup-steps.yml

[SteveSandersonMS]

@copilot Shouldn't we add the uv.lock file instead?

[Copilot]

@copilot Shouldn't we add the uv.lock file instead?

uv.lock is intentionally in python/.gitignore (line 167) — this is standard practice for libraries/SDKs where you don't want to pin exact transitive dependency versions. All other workflows in the repo (python-sdk-tests.yml, docs-validation.yml) already use uv sync without --locked, so this PR aligns copilot-setup-steps.yml with the existing convention.