Explore switching back to absolute imports in core

[mjbvz]

As part of the esm migration, we switch all of the imports to relative paths. This makes it more difficult to know where a file is coming from and also makes it harder to move around code. I'd like to see if we can switch back to absolute paths instead

In #236640 I'm switching us to use nodenext for module resolution to fix a few other issues (such as no errors on extension less imports). This also will also let us use import path mapping

For this, we just need to add this to the package.json:

  "imports": {
    "#vs/*.js": "./src/vs/*.js"
  },

Then we can write import { ILogService } from '#vs/platform/log/common/log.js' and TS will be able to resolve the right file

We still need to figure out how to get our loader understanding these paths