T7641: Trigger rebuild VPP binaries if vyos-vpp-patches changed

[sever-sever]

Change Summary

Trigger to rebuild vpp binaries if we changed something in our patches

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Code style update (formatting, renaming)
• Refactoring (no functional changes)
• Other (please describe): CI trigger package rebuild

Related Task(s)

• https://vyos.dev/T7641

Related PR(s)

Proposed changes

How to test

Checklist:

• I have read the CONTRIBUTING document
• I have linked this PR to one or more Phabricator Task(s)
• My commit headlines contain a valid Task id
• My change requires a change to the documentation
• I have updated the documentation accordingly

[Copilot]

Pull Request Overview

This PR adds a GitHub workflow to automatically trigger rebuilding of VPP (Vector Packet Processing) binaries when patches are modified in the vyos-vpp-patches repository. The workflow monitors changes to VPP patches and initiates a rebuild of the corresponding VPP package to ensure the binaries reflect the latest patch modifications.

• Adds automated detection of changes to VPP patches in the patches/vpp/ directory
• Implements conditional triggering that only rebuilds VPP package when patches are actually modified
• Integrates with existing reusable workflow infrastructure for package rebuilding

Comments suppressed due to low confidence (1)

.github/workflows/trigger-rebuild-repo-package.yml:37

• [nitpick] The workflow file name and the reusable workflow being called have the same name 'trigger-rebuild-repo-package.yml'. This could cause confusion. Consider renaming this file to something more specific like 'trigger-vpp-rebuild.yml' to clearly distinguish its purpose.

    uses: vyos/.github/.github/workflows/trigger-rebuild-repo-package.yml@current