docs-test: improve logging

[dgn]

logs of individual tests are now written to their own files in the prow artifacts directory. also, start, ending and individual steps in a test are printed differently so that it's easier to navigate the logs.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.38%. Comparing base (43234a9) to head (c5b25b7).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1433      +/-   ##
==========================================
- Coverage   80.77%   80.38%   -0.40%     
==========================================
  Files          44       44              
  Lines        2299     2299              
==========================================
- Hits         1857     1848       -9     
- Misses        324      330       +6     
- Partials      118      121       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[dgn]

Example output from docs-test job:

##### Test dual-stack: start


##### Test dual-stack: Step 1: Create the Istio resource with dual-stack configuration.

Error from server (NotFound): namespaces "istio-system" not found
namespace/istio-system created
istio.sailoperator.io/default created
istio.sailoperator.io/default condition met

##### Test dual-stack: Step 2: Create the following namespaces, each hosting the tcp-echo service with the specified configuration.

Error from server (NotFound): namespaces "dual-stack" not found
namespace/dual-stack created
Error from server (NotFound): namespaces "ipv4" not found
namespace/ipv4 created
Error from server (NotFound): namespaces "ipv6" not found
namespace/ipv6 created
Error from server (NotFound): namespaces "sleep" not found
namespace/sleep created

##### Test dual-stack: Step 3: Label the namespaces for sidecar injection.

namespace/dual-stack labeled
namespace/ipv4 labeled
namespace/ipv6 labeled
namespace/sleep labeled

##### Test dual-stack: Step 4: Deploy the pods and services in their respective namespaces.

service/tcp-echo created
deployment.apps/tcp-echo created
service/tcp-echo created
deployment.apps/tcp-echo created
service/tcp-echo created
deployment.apps/tcp-echo created
serviceaccount/sleep created
service/sleep created
deployment.apps/sleep created
pod/sleep-7cccf64445-4cccv condition met
pod/tcp-echo-b44db6ccc-dn8zw condition met
pod/tcp-echo-b44db6ccc-vtm2p condition met
pod/tcp-echo-b44db6ccc-s7mxm condition met

##### Test dual-stack: Step 5: Ensure that the tcp-echo service in the dual-stack namespace is configured with ipFamilyPolicy of RequireDualStack.

RequireDualStack
ipFamilyPolicy is set to RequireDualStack as expected

##### Test dual-stack: Step 6: Verify that sleep pod is able to reach the dual-stack pods.

hello dualstack
Sleep can reach tcp-echo.dual-stack pod as expected

##### Test dual-stack: Step 7: Similarly verify that sleep pod is able to reach both ipv4 pods as well as ipv6 pods.

hello ipv4
Sleep can reach tcp-echo.ipv4 pod as expected

##### Test dual-stack: Step 8

hello ipv6
Sleep can reach tcp-echo.ipv6 pod as expected

##### Test dual-stack completed: PASS

[fjglira]

Example output from docs-test job:

##### Test dual-stack: start


##### Test dual-stack: Step 1: Create the Istio resource with dual-stack configuration.

Error from server (NotFound): namespaces "istio-system" not found
namespace/istio-system created
istio.sailoperator.io/default created
istio.sailoperator.io/default condition met

##### Test dual-stack: Step 2: Create the following namespaces, each hosting the tcp-echo service with the specified configuration.

Error from server (NotFound): namespaces "dual-stack" not found
namespace/dual-stack created
Error from server (NotFound): namespaces "ipv4" not found
namespace/ipv4 created
Error from server (NotFound): namespaces "ipv6" not found
namespace/ipv6 created
Error from server (NotFound): namespaces "sleep" not found
namespace/sleep created

##### Test dual-stack: Step 3: Label the namespaces for sidecar injection.

namespace/dual-stack labeled
namespace/ipv4 labeled
namespace/ipv6 labeled
namespace/sleep labeled

##### Test dual-stack: Step 4: Deploy the pods and services in their respective namespaces.

service/tcp-echo created
deployment.apps/tcp-echo created
service/tcp-echo created
deployment.apps/tcp-echo created
service/tcp-echo created
deployment.apps/tcp-echo created
serviceaccount/sleep created
service/sleep created
deployment.apps/sleep created
pod/sleep-7cccf64445-4cccv condition met
pod/tcp-echo-b44db6ccc-dn8zw condition met
pod/tcp-echo-b44db6ccc-vtm2p condition met
pod/tcp-echo-b44db6ccc-s7mxm condition met

##### Test dual-stack: Step 5: Ensure that the tcp-echo service in the dual-stack namespace is configured with ipFamilyPolicy of RequireDualStack.

RequireDualStack
ipFamilyPolicy is set to RequireDualStack as expected

##### Test dual-stack: Step 6: Verify that sleep pod is able to reach the dual-stack pods.

hello dualstack
Sleep can reach tcp-echo.dual-stack pod as expected

##### Test dual-stack: Step 7: Similarly verify that sleep pod is able to reach both ipv4 pods as well as ipv6 pods.

hello ipv4
Sleep can reach tcp-echo.ipv4 pod as expected

##### Test dual-stack: Step 8

hello ipv6
Sleep can reach tcp-echo.ipv6 pod as expected

##### Test dual-stack completed: PASS

This is amazing, way better than looking into the actual logs

[fjglira]

LGTM, I really like this change, improve a lot the readability of the test result and make easier to debug errors