ci(v3): test and lint v-next packages lazily

[galargh]

• Because this PR includes a bug fix, relevant tests have been included.
• Because this PR includes a new feature, the change was previously discussed on an Issue or with someone from the team.
• I didn't do anything of this.

---

This PR is a subset of #5301 and, unlike the original, it targets the v-next branch.

In this PR, I introduce the notion of deciding what packages to build in CI lazily. The intention is to build and test only these packages that were themselves modified or if one of their local dependencies (including transitive dependencies) were modified.

To achieve this, I added a script which parses the pnpm lockfile, builds up a map of local transitive depencies out of it, and outputs a filter that can be used directly with https://github.com/dorny/paths-filter (an action that filters a list of packages based on the modified paths).

The output of the script I added can be controlled with 2 environment variables: PACKAGE_IGNORE (to filter out the packages that we don't care about) and COMMON_FILTERS (to configure glob paths which modification should result in building all the packages).

Example

In our script execution, we want to exclude the root package, the v2 packages and the example-project so we set PACKAGE_IGNORE=["packages/", ".", "v-next/example-project"].

We also want to ensure that modifying anything under config-v-next builds all of the packages so we set COMMON_FILTERS=["config-v-next/**"].

The output of our script (after parsing it with `yq`) would be:

core:
  - config-v-next/**
  - v-next/core/**
  - v-next/hardhat-errors/**
  - v-next/hardhat-utils/**
  - v-next/hardhat-node-test-reporter/**
  - v-next/hardhat-test-utils/**
hardhat:
  - config-v-next/**
  - v-next/hardhat/**
  - v-next/core/**
  - v-next/hardhat-errors/**
  - v-next/hardhat-utils/**
  - v-next/hardhat-zod-utils/**
  - v-next/hardhat-node-test-reporter/**
  - v-next/hardhat-test-utils/**
hardhat-build-system:
  - config-v-next/**
  - v-next/hardhat-build-system/**
  - v-next/hardhat-errors/**
  - v-next/hardhat-utils/**
  - v-next/hardhat-node-test-reporter/**
  - v-next/hardhat-test-utils/**
hardhat-errors:
  - config-v-next/**
  - v-next/hardhat-errors/**
  - v-next/hardhat-utils/**
  - v-next/hardhat-node-test-reporter/**
hardhat-node-test-reporter:
  - config-v-next/**
  - v-next/hardhat-node-test-reporter/**
hardhat-test-utils:
  - config-v-next/**
  - v-next/hardhat-test-utils/**
  - v-next/hardhat-errors/**
  - v-next/hardhat-utils/**
  - v-next/hardhat-node-test-reporter/**
hardhat-utils:
  - config-v-next/**
  - v-next/hardhat-utils/**
  - v-next/hardhat-node-test-reporter/**
hardhat-zod-utils:
  - config-v-next/**
  - v-next/hardhat-zod-utils/**
  - v-next/core/**
  - v-next/hardhat-node-test-reporter/**
  - v-next/hardhat-test-utils/**
  - v-next/hardhat-errors/**
  - v-next/hardhat-utils/**
template-package:
  - config-v-next/**
  - v-next/template-package/**
  - v-next/hardhat-node-test-reporter/**
  - v-next/hardhat-test-utils/**
  - v-next/hardhat-errors/**
  - v-next/hardhat-utils/**

Now, let's say we modify v-next/hardhat-zod-utils/package.json. If we, then, used the script output as the input to dorny/paths-filter action, we would learn that we should build only the following packages:

• hardhat
• hardhat-zod-utils

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
hardhat	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 2, 2024 4:10pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: f8dc86c

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

[alcuadrado]

When a lockfile is modified we should run everything

[galargh]

I added pnpm lockfile handling in f8dc86c