Right now, we use a consolidated lockfile at the root of the monorepo. This, although efficient, does not allow us to detect changes on specific packages.

When we update a dependency in any of the packages, the root lock file is updated, which makes us have to build the entire monorepo, since we can't detect which packages need to be rebuilt to make sure that this change is good.

pnpm has a flag for that, so installing with `
pnpm install -r --shared-workspace-lockfile=false --strict-peer-dependencies=false` will create those individual lock files.
 
It's expected that after this research, we're able to simulate a scenario where a PR updates/adds/removes a dependency, and our CI is able to only build the necessary packages.
 
We should also be able to tell which are the advantages and disadvantages of this approach, researching other people's use-cases, issues on `pnpm` and other monorepo resources.
 
After the analysis is done, we can move forward and go ahead with the change, or not.