[MSBUILD SDK] Support publish for Resolver.csproj

[jviau]

Issue describing the changes in this PR

resolves #issue_for_this_pr

Pull request checklist

• My changes do not require documentation changes
  • Otherwise: Documentation issue linked to PR
• My changes should not be added to the release notes for the next release
  • Otherwise: I've added my notes to release_notes.md
• My changes do not need to be backported to a previous version
  • Otherwise: Backport tracked by issue/PR #issue_or_pr
• I have added all required tests (Unit tests, E2E tests)

Additional information

Adding ability to publish the resolver. I found this useful for consuming the SDK locally for debugging/inner dev loop. Now you can simply dotnet publish the resolver project, and then run init.ps1 from the publish location.

[Copilot]

Pull Request Overview

This PR adds support for using the Azure.Functions.Sdk.Resolver locally during development by enhancing the publish workflow. The changes enable developers to publish the resolver and use a generated PowerShell script to configure their environment for debugging.

Key changes:

• Added MSBuild properties to control output file copying during build and publish
• Split SDK file collection into separate targets for build and publish scenarios
• Added automatic generation of an init.ps1 script during publish
• Updated documentation with instructions for local usage

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
Azure.Functions.Sdk.Resolver.csproj	Enhanced build/publish configuration with new properties, refactored targets to handle build and publish separately, and added script generation target
README.md	Added new section documenting local usage workflow with the generated init.ps1 script

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.