fix: source-maps - consistent paths to inline content - #39302

Hmm, CI points out that this does not really work well... I think we need a better solution...

I've realised that we cannot fix things this way. By hacking the source path for inline files we end up losing the path to the original source in a way that would break i18n extraction. See the integration test results from this PR:

Error: Expected

<source>Message in <x id="a-file" equiv-text="file"/>!</source>
<context-group purpose="location">
  <context context-type="sourcefile">test_files/dist_es5/a.ts</context>
  <context context-type="linenumber">3,5</context>
</context-group>

to equal

<source>Message in <x id="a-file" equiv-text="file"/>!</source>
<context-group purpose="location">
  <context context-type="sourcefile">../packages/localize/src/tools/test/extract/integration/test_files/src/a.ts</context>
  <context context-type="linenumber">3,5</context>
</context-group>

(Note that the path we would really like is test_files/src/a.ts but this PR results in test_files/dist_es5/a.ts which is confusing because the original source file is not in dist_es5 since this is where the generated file is - i.e. dist_es5/index.js)

I'm not sure if we can actually fix the problem from this side. We may need to return to the original cause #14021

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}