add a job for existing tests in ambient mode

[stevenctl]

This deserves some discussion, but I think it adds valuable coverage.
It could also be accomplished by forcing the "everywhere" mode in Go code.

This invocation without the ambient.everywhere flag results in mostly testing sidecars (I think with HBONE turned on?). We end up skipping a lot. If we grep down to to_waypoint|from_captured|to_captured we only gain coverage on the virtualservice cases.

When we run with the everywhere flag, pretty much all our apps get a waypoint. This means we cover pretty much all of the L7 functionality. (That isn't explicitly skipped, which is still a lot).

2023-09-07T19:36:29.084617Z	info	tf	adding waypoint to /a
2023-09-07T19:36:29.084623Z	info	tf	adding waypoint to /b
2023-09-07T19:36:29.084627Z	info	tf	adding waypoint to /c
2023-09-07T19:36:29.084631Z	info	tf	adding waypoint to /headless
2023-09-07T19:36:29.084635Z	info	tf	adding waypoint to /statefulset
2023-09-07T19:36:29.084640Z	info	tf	adding waypoint to /naked
2023-09-07T19:36:29.084644Z	info	tf	adding waypoint to /tproxy
2023-09-07T19:36:29.084649Z	info	tf	adding waypoint to /vm

---

I intend to expand this job to run pilot rather than ambient with -run TestTraffic. That will rely on istio/istio#46863 and enumerating valuable tests/and valid skips.

[istio-policy-bot]

😊 Welcome @stevenctl! This is either your first contribution to the Istio test-infra repo, or it's been
awhile since you've been here.

You can learn more about the Istio working groups, code of conduct, and contributing guidelines
by referring to Contributing to Istio.

Thanks for contributing!

Courtesy of your friendly welcome wagon.