Don't run Telescope tests on Waterfall updates

Looks like we run both Telescope and Waterfall tests when waterfall packages are updated.

Telescope tests are time and resource consuming and unnecessary in this case.

Only run them for `packages/telescope` files.

Start by locating the CI workflow or test-selection entry point that runs Telescope and Waterfall tests for package updates. Trace how changed paths are detected, then verify that updates outside packages/telescope skip Telescope tests while packages/telescope changes still run them.

Written by the indexing model from the issue text.