Update branch pattern for FOSSA scanning

[ihcsim]

Problem:

Follow-up on #260 (comment) - update FOSSA scan workflow to watch the correct release branches.

[Copilot]

Pull request overview

This PR updates the FOSSA scanning workflow to use a more specific branch pattern for release branches, changing from release/** to v[0-9]+.[0-9]+ to match version-based branch names.

Changes:

• Modified the branch trigger pattern in the FOSSA workflow from release/** to v[0-9]+.[0-9]+ to align with the repository's release branch naming convention

---

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

[Copilot]

The branch pattern v[0-9]+.[0-9]+ is incorrect for GitHub Actions workflow triggers. In glob patterns, the dot (.) is interpreted literally as any single character, not just a period. This means the pattern would incorrectly match branch names like v1X2 in addition to v1.2.

For consistency with other workflows in this repository (basic-ci.yaml and scan.yml), the pattern should be 'v**' to match all version branches starting with 'v'. Alternatively, if you need to match only semantic version patterns, you should use v[0-9]+.[0-9]+* to allow for patch versions like v1.2.3.

Suggested change

	branches: ["main", "master", "v[0-9]+.[0-9]+"]
	branches: ["main", "master", "v**"]