Fix API sync agent workflow after DynamicData rename

[Copilot]

The agent job in the weekly API sync workflow was failing because the prompt and safe-output allowlist still referenced the pre-rename R3.DynamicData path, and the agent instructions encouraged broad repository reads that drove token usage into the hard limit. This change aligns the workflow with the current repo layout and narrows the agent’s decision path.

• Workflow path alignment

  • Update the API sync prompt front matter to allow edits under R3Ext.DynamicData/**/*.cs
  • Mirror the same path fix in the generated safe-outputs config embedded in api-sync-check.lock.yml

• Prompt scope reduction

  • Tell the agent to noop early when recent upstream changes do not affect public API surface
  • Instruct the agent to inspect only targeted files/snippets tied to candidate upstream changes instead of reading large areas of the repo

• Repository context refresh

  • Replace stale R3.DynamicData/ references in the workflow prompt with R3Ext.DynamicData/ so the agent reasons about the current project structure

safe-outputs:
  create-pull-request:
    allowed-files:
      - "R3Ext/**/*.cs"
      - "R3Ext.DynamicData/**/*.cs"