chore: reorganize tsconfig files for clarity

[ulissesferreira]

Explanation

One more clarity improving PR for the tsconfig files on our repository so anyone can understand what is happening under the hood and keeping as many similarities as possible with core. The hierarchy of the config files is explained below but I believe that with their names and comments inside it should be self explanatory. Please raise if this is not extremely intuitive.

tsconfig.base.json                              - Configurations shared by all `tsconfig` files
│
├── tsconfig.json                               - Repository root configuration
├── tsconfig.scripts.json                       - Used for the `scripts/` directory
└── tsconfig.packages.json                      - Shared by all `packages/`, whether Snaps or not
    │
    ├── 👻 tsconfig.packages.non-snaps.json     - Not needed because it's the same thing as
    │                                             `tsconfig.packages.json`
    ├── tsconfig.packages.non-snaps.build.json  - Needed changed for the emission of
    │                                             declarations
    │
    ├── tsconfig.packages.snaps.json            - Snap specific configurations
    └── 👻 tsconfig.packages.snaps.build.json   - Not needed because mm-snap handles
                                                    everything automatically

References

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

[taran-a]

LGTM. GG

[Battambang]

3 levels isn't it make it outside the repo from this tree level?

[Battambang]

also might be too deep here