Add yarn changesets

[yorhodes]

Description

• monorepo commands will only run for packages which have changed since baseRef: main

Drive-by changes

• modify github actions to leverage filtered behavior
• upgrade to yarn 4.0.2

Related issues

• Fixes https://github.com/hyperlane-xyz/issues/issues/708
• Fixes https://github.com/hyperlane-xyz/issues/issues/374

Backward compatibility

Testing

[changeset-bot]

⚠️ No Changeset found

Latest commit: db58ae1

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

[aroralanuk]

Where did you put the test-sol job, it's missing from node.yaml? Also coverage should be triggered on `solidity/* path too?

[yorhodes]

Where did you put the test-sol job, it's missing from node.yaml? Also coverage should be triggered on `solidity/* path too?

I renamed it because it now includes the sol and ts tests
coverage will be triggered for any workspace that has a diff, including solidity

[aroralanuk]

Where did you put the test-sol job, it's missing from node.yaml? Also coverage should be triggered on `solidity/* path too?

I renamed it because it now includes the sol and ts tests coverage will be triggered for any workspace that has a diff, including solidity

isn't this adding time and blocking non-solidity tests by checking solidity tests

[yorhodes]

I renamed it because it now includes the sol and ts tests coverage will be triggered for any workspace that has a diff, including solidity

isn't this adding time and blocking non-solidity tests by checking solidity tests

for some PRs, it may result in a slight increase in runtime yes...
the test-sol dominated runtime anyway so I think this should be fine