Re-export the "module_name" attribute of ts_library as a provider.

This lets downstream rules like Angular see the module_name and use it for packaging.

Note that we also have a module_mapping aspect which collects up a mapping usable for TypeScript pathMapping, but this doesn't indicate which key belongs to this target vs. its dependencies.

PiperOrigin-RevId: 192685304

internal/common/compilation.bzl

@@ -376,6 +376,10 @@ def compile_ts(ctx,
       },
       # Expose the tags so that a Skylark aspect can access them.
       "tags": ctx.attr.tags,
+      # Expose the module_name so that packaging rules can access it.
+      # e.g. rollup_bundle under Bazel needs to convert this into a UMD global
+      # name in the Rollup configuration.
+      "module_name": ctx.attr.module_name,
       "instrumented_files": {
           "extensions": ["ts"],
           "source_attributes": ["srcs"],