ci: add CI for checking generated changesets

[cabljac]

No description provided.

[docs-page]

To view this pull requests documentation preview, visit the following URL:

docs.page/invertase/tanstack-query-firebase~196

Documentation is deployed and generated using docs.page.

[Copilot]

Pull Request Overview

This PR adds CI validation to ensure that changesets are created when packages are modified. The CI workflow now checks for package changes and enforces the presence of corresponding changesets to maintain proper release management.

• Adds changeset validation to the quality job in the tests workflow
• Updates changeset commands to use more robust find operations instead of shell globbing
• Adds fetch-depth: 0 to checkout actions to enable proper git history access

Reviewed Changes

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

File	Description
.github/workflows/tests.yaml	Adds changeset validation step and configures full git history checkout
.github/workflows/release.yml	Updates changeset validation commands to use more robust file finding

Comments suppressed due to low confidence (1)

.github/workflows/tests.yaml:38

• The step ID 'quality-changes' is misleading since this step determines package changes, not quality changes. Consider renaming to 'package-changes' or 'changed-packages' for clarity.

        id: quality-changes

[Copilot]

The condition logic is duplicated in lines 50, 59, and 62. Consider storing the package change detection in a variable or using a more maintainable approach to avoid repetition.

Suggested change

	if [[ "${{ steps.quality-changes.outputs.react }}" == "true" ]] || [[ "${{ steps.quality-changes.outputs.angular }}" == "true" ]]; then
	packages_changed=$([[ "${{ steps.quality-changes.outputs.react }}" == "true" ]] || [[ "${{ steps.quality-changes.outputs.angular }}" == "true" ]])
	if [[ "$packages_changed" == "true" ]]; then