chore: Reduce the scope of changeset to src folder

[milosh86]

Description

Reduce the scope of changeset to src folder to avoid adding empty changeset when updating dependencies or other chore updates.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Developer Checklist:

• Manually smoke tested the functionality locally
• Confirmed there are no new warnings or errors in the browser console
• Made the corresponding changes to the documentation
• Added tests that prove my fix is effective or that my feature works
• (For User Stories only) Double-checked that all Acceptance Criteria are satisified
• Confirmed there are no new warnings on automated tests
• Selected the correct base branch
• Commented the code in hard-to-understand areas
• Followed the code style guidelines of this project
• Reviewed that the files changed in GitHub’s UI reflect my intended changes
• Confirmed the pipeline checks are not failing

Review Checklist:

• Tested locally that all Acceptance Criteria or Expected Outcomes are satisfied
• Confirmed that changes follow the code style guidelines of this project

[Copilot]

Pull Request Overview

This PR configures the changeset tool to only track changes within the src folder, preventing empty changesets from being generated when updating dependencies or making other non-source code changes.

• Adds changedFilePatterns configuration to limit changeset scope to source code

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[thekidnamedkd]

LGTM ✨