fix(bazel): ng test should run specific ts_web_test_suite

[kyliau]

PR closes #30191

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit
• 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
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• angular.io application / infrastructure 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]

I would just add in the commit message why the change is needed and that it assumes that the BUILD files are the ones generated by ng new.

The downside of this is that if you leave BUILD files on disk and add more tests than ng test will no longer run all tests which may be unexpected. Maybe Alex's suggestion to mark rollup_bundle as "manual" would be better?

[mgechev]

This LGTM but I'll let @alexeagle & @gregmagolan give the final approval.

[alexeagle]

I agree with @gregmagolan that users may get confused over the behavior when they start to customize the build, but they'll have to understand which targets to run when they do that. This would be a good fix for 8

[angular-automatic-lock-bot]

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.}