build: improve ts_project interop to work with esbuild bundling

Improves the `ts_project` interop to work with Esbuild bundling. Right
now we can end up with multiple copies of the same source file.

e.g. input might import from `@angular/cdk/testing` and end up with
the version of `rules_nodejs` linker, while other imports to the native
`ts_library` targets end up being mapped to their actual sources in the
`bazel-bin`, and not inside `node_modules`

Author: devversion

tools/bazel/ts_project_interop.bzl

@@ -2,6 +2,7 @@ load("@aspect_rules_js//js:providers.bzl", "JsInfo", "js_info")
 load("@aspect_rules_ts//ts:defs.bzl", _ts_project = "ts_project")
 load("@build_bazel_rules_nodejs//:providers.bzl", "DeclarationInfo", "JSEcmaScriptModuleInfo", "JSModuleInfo", "LinkablePackageInfo")
 load("@devinfra//bazel/ts_project:index.bzl", "strict_deps_test")
+load("@build_bazel_rules_nodejs//internal/linker:link_node_modules.bzl", "LinkerPackageMappingInfo")
 
 def _ts_deps_interop_impl(ctx):
     types = []
@@ -81,6 +82,18 @@ def _ts_project_module_impl(ctx):
                 files = info.sources,
             ),
         )
+        providers.append(
+            LinkerPackageMappingInfo(
+                mappings = depset([
+                    struct(
+                        package_name = ctx.attr.module_name,
+                        package_path = "",
+                        link_path = ctx.label.package,
+                    ),
+                ]),
+                node_modules_roots = depset([]),
+            ),
+        )
 
     return providers