chore: export TsConfigInfo in public interface

[sallustfire]

PR Checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature (please, look at the "Scope of the project" section in the README.md file)
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe: Add API export

What is the current behavior?

The typescript package @npm//@bazel/typescript:index.bzl exports the public typescript rules interface including a rule called ts_config. However, ts_config returns a provider TsConfigInfo that is not publicly exported and is instead found under @rules_nodejs//nodejs/private:ts_config.bzl.

Issue Number: N/A

What is the new behavior?

TsConfigInfo is exported from @npm//@bazel/typescript:index.bzl alongside ts_config.

Does this PR introduce a breaking change?

• Yes
• No

Other information

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[alexeagle]

@sallustfire can you make the CLA bot happy? Google wants to have IP rights to all the code.

[sallustfire]

Yep, looks like it is happy now. Let me know if you need anything else.