ci: Choose correct path to tinylicious.log depending on realsvc or stress tests

[alexvy86]

Description

Currently when we run the stress tests against tinylicious (in the build pipeline, not in the separate pipeline for stress tests), the step to upload the tinylicious log to the pipeline artifacts logs a warning because it's looking for the log file in the wrong place (the path where the file ends up in when the real-svc tests run, but not when the stress tests run).

This adds logic to look for the log file in the correct place in each case.

Reviewer Guidance

The review process is outlined on this wiki page.

Run from this PR demonstrates the log file is now uploaded correctly for the stress tests and for the real-svc tests.

I deliberately did not try to check for the exact test script being run (e.g. ci:test:realsvc:tinylicious VS ci:test:stress:tinylicious) to avoid future issues if we change the script names. The new logic could potentially also break during a drastic rename, but I think has a better chance of surviving a small script name refactor.

[Copilot]

Pull request overview

Updates the client build pipeline template to upload tinylicious.log from the correct package directory depending on whether the run is for real-service tinylicious tests or stress tinylicious tests, avoiding artifact-upload warnings in CI.

Changes:

• Passes the current test.name into the “Upload tinylicious log” Bash task via TEST_NAME.
• Adds Bash logic to select the correct package directory (test-end-to-end-tests vs test-service-load) before uploading tinylicious.log.