chore: better eslint

[andreabadesso]

Motivation

The motivation for the changes in this PR is to fix ESLint issues in editors by ensuring each project gets the correct ESLint configuration. Currently, ESLint is failing because it is unable to correctly parse TypeScript files for each project.

Acceptance Criteria

• Ensure ESLint correctly parses TypeScript files for the common, daemon, and wallet-service packages.
• Update the Nix flake configuration to properly inherit nodePackages and configure the development shell.
• Add TypeScript dependency to the project root
• Introduce a new tsconfig.json in the root importing packages tsconfigs

Checklist

• If you are requesting a merge into master, confirm this code is production-ready and can be included in future releases as soon as it gets merged.
• Make sure either the unit tests and/or the QA tests are capable of testing the new features.
• Make sure you do not include new dependencies in the project unless strictly necessary and do not include dev-dependencies as production ones. More dependencies increase the possibility of one of them being hijacked and affecting us.

[tuliomir]

question(non-blocking): While I think adding the .bin folder to the path is a smart move, maybe it relies too much on the internal implementation of NodeJS.

What is our actual need for this export? Couldn't we just replace our usage of those binaries with npx myDependency, since npx is available since npm 8?

[andreabadesso]

Yea, the idea here is to have typescript available in the path, so the LSP from the dev editor can use it

This it good so we don't have to install typescript globally (using npm)

Also, we are using yarn in this repository, so we shouldn't use npm here