ci: optimize test workflows for directory-specific changes (#265)

[7fighter]

This PR implements directory-specific test triggering to optimize CI resources as requested in #265.

Changes

• Added dorny/paths-filter to pull-request.yml to detect changes in core, web, and react-native directories.
• Updated verify.yml to accept these detections as inputs and conditionalize job execution.
• Ensured lint runs for any relevant changes while heavy builds are scoped to their specific domains.
• Fixed Prettier formatting issues in the workflow files.

Verification (Tested on fork)

• React Native change: Only Lint and RN Build triggered.
• Core/Web change: Relevant test suites triggered.
• Workflow change: Full suite triggered (expected behavior).

Fixes #265

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1d0b60b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[MrImmortal09]

@7fighter Check out the changeset.yml to understand how the react-native building works.

You will need a mac os runner for building the ios, so that should be a seperate task, keep rest tasks on self hosted linux runners.

[MrImmortal09]

@alexlwn123 Should we run all the tests if any of the workflow changes?

This event happens rarely, but ig the tests should be checked before we merge.

[alexlwn123]

Should we run all the tests if any of the workflow changes?

This event happens rarely, but ig the tests should be checked before we merge.

Agree, seems like a good sanity check.

[MrImmortal09]

@7fighter Please run all the tests if any of the workflow changes.

[MrImmortal09]

@7fighter Do check this out.

[MrImmortal09]

The submodules isn't getting initialised properly in a few checks.

[MrImmortal09]

the react-native-android tries to build android(pnpm ubrn:android) but fails due to absense of fedimint-sdk-ffi, and the react-native-ios tries to build both android and ios bindings. The android bindings are thus build twice.