chore: automatically generate tsconfigs

[legendecas]

Which problem is this PR solving?

Fixes #3398

Short description of the changes

1. Split tsconfig into 3 root entries: default, esnext, esm.
   1. When testing locally, found that when tsconfig targets which are referenced share identical source files, some targets will not output files correctly. So splitting them into different compilation units.
2. Compile all tsconfig entries when running npm run compile.

Type of change

• Internal house keeping.

Checklist:

• Followed the style guidelines of this project

[codecov]

Codecov Report

Merging #3432 (1b935f2) into main (ed98c6f) will decrease coverage by 0.01%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3432      +/-   ##
==========================================
- Coverage   93.29%   93.28%   -0.02%     
==========================================
  Files         247      247              
  Lines        7352     7352              
  Branches     1512     1512              
==========================================
- Hits         6859     6858       -1     
- Misses        493      494       +1     

Impacted Files	Coverage Δ
...-trace-base/src/platform/node/RandomIdGenerator.ts	87.50% <0.00%> (-6.25%)	⬇️

[pichlermarc]

Thanks for working on this. 🙂
Looks like there are some hiccups but after applying the suggestions this works for me locally. 🙂

[dyladan]

Also works for me locally after @pichlermarc changes (macos). Applied them.