ci(development): update workflow path filters for detecting changes

[coreyhn]

Add platform native library files to Rust change detection. This allows force rebuilds by deleting libraries when a clean rebuild of all platforms is needed. This approach integrates cleanly with the existing PR workflow without requiring manual workflow triggers or version bumps.

The library commit in PR #8 failed to update all platforms, maybe due to a transient issue with the commit action. A validation step may be needed if this rebuild resolves the issue.

[coreyhn]

There is still an issue with the committed libraries. This is due to the use of the getsentry/action-github-commit action:

protectphp-ffi/.github/workflows/development.yml

Lines 394 to 401 in 144c52b

	- name: Commit all native libraries
	uses: getsentry/action-github-commit@v2.0.0
	with:
	github-token: ${{ secrets.GITHUB_TOKEN }}
	message: |
	build(platforms): update all native libraries
	Source: ${{ steps.source-commit.outputs.sha }}

The .gitattributes file should prevent this, but this action bypasses git's normal text/binary detection and reads all files as buffers and then converts them to UTF-8 strings with Buffer.toString(), causing binary data to be corrupted with UTF-8 replacement characters:

# Working library from build job before commit
platforms/darwin-x64/libprotect_ffi.dylib: Mach-O 64-bit dynamically linked shared library x86_64

# Corrupted library in branch after commit
platforms/darwin-x64/libprotect_ffi.dylib: data

# File size comparison
Working:    2861156 bytes
Corrupted:  4781434 bytes

# Hex dump comparison (first 32 bytes)
Working:
00000000  cf fa ed fe 07 00 00 01  03 00 00 00 06 00 00 00  |................|
00000010  10 00 00 00 88 08 00 00  85 00 90 00 00 00 00 00  |................|
Corrupted:
00000000  ef bf bd ef bf bd ef bf  bd ef bf bd 07 00 00 01  |................|
00000010  03 00 00 00 06 00 00 00  10 00 00 00 ef bf bd 08  |................|

I added this action right before PR #1 to get verified commits by github-actions[bot] by using the GitHub API instead of using normal git operations (and having to manage GPG keys). The commits are "verified," but the libraries are definitely not.