test(Karma): add e2e test for Karma files collected through sources_aspect

[kyliau]

Karma should only load explicit node_sources and dev_scripts from
its deps and runtime_deps. There should not be a case where Karma
needs to load all files in a target.

For third-party deps, an explicit file from the package should be
provided to Karma instead of the entire package.
For example, @npm//node_modules/rxjs:bundles/rxjs.umd.js should
be used instead of @npm//rxjs.

(This effectively means devserver and Karma do not know how to
serve node modules that are not in APF format, so users have to
explicitly specify the files instead of Karma blindly loading everything).

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:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

[gregmagolan]

Looks right to me. The karma rule is getting confusing with all the different types of deps. I started a cleanup at one point to make the code clearer and got halfway through. Maybe time to dig that up again.

[alexeagle]

can you consolidate this into an existing e2e and keep the same assertions?
we shouldn't continue to have new e2e for each

[kyliau]

can you consolidate this into an existing e2e and keep the same assertions?
we shouldn't continue to have new e2e for each

done, merged into existing karma_typescript e2e.