Bug: Chromium Platform does not fully use Stealify Lang

[lemanschik]

Chromium Platform does not use Stealify Lang to build 100% of it self.

Rewriting incremental strategies to upgrade the chromium build process in a way that google accepts it and all contributors can adopt it is beneficial while not needed as soon as we come up with more and more components and modules rewritten in the new pattern used Stealify Lang we can even supersede them.

• NodeJS is still part of the ecosystem and platform
  • Bug: NodeJS depends on NPM #21
  • Should get replaced by the chromium platform it self via better Visual Build tools
• V8 Related Self build state
  • Linux Works just flawless
• As bespoken with the creator of MESON we enable MESON build syntax via Stealify Lang.
  • Strategic initiative: future of Node.js build toolchain nodejs/TSC#901 @eli-schwartz
• Better GN Ninja adoption patterns and docs
• Better Python Deprecation docs and patterns
• Better Module System declared via resolvers in the root directory as everything is a component everything forks from the root and everything can be a submodule or composition out of git submodules.
• Enables both development flows incremental partial checkout without extra tooling via worktrees and branches
• Whole Platform checkout via submodule init fetch all.
• Creating individual composed reference only repos only out of submodules that lead to ultra fast checkouts and sync.
• nncp support zero overhead text compression out of the box to even more speed up sync.
• Better faster goma integration reuse of apis
• upgrade the c++ code if possible to just components and cpp 20 or even cpp2 if possible
  • use our b8g server build of the chromium platform for best most small interop modules. including mojo bindings for ecmascript