Add configurable ReleaseFiles parameter for release-triggering file patterns

[Copilot]

Release-triggering file patterns (e.g., action.yml, src/**) were hardcoded in the workflow paths filter. Users had no way to control which file changes should warrant a release.

Changes

• action.yml: New ReleaseFiles input — comma-separated glob patterns, default empty (opt-in, fully backward compatible)
• src/main.ps1: Read ReleaseFiles from config file or input, match PR changed files via gh pr diff --name-only against patterns using -like, skip release if nothing matches
• README.md: Document ReleaseFiles in settings table and config file example

Usage

As an action input:

- uses: PSModule/Release-GHRepository@v1
  with:
    ReleaseFiles: 'action.yml, src/**'

Or in .github/auto-release.yml:

ReleaseFiles: 'action.yml, src/**'

When ReleaseFiles is empty (default), all file changes trigger releases — no behavior change for existing users.

Original prompt

/create-issue Make an issue where we add the option for important files that warrant a new release as parameters/inputs/config items in the settings file that the user can use to override the default behavior for what a release is. Today this is hardcoded into the action/workflow.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.