Run copy results after tests failures

[dannimad]

Updating pipeline conditions to run copy results even after tests failures.

• Condition was missing from non coverage tests
• Reinforcing usage of variables created before running tests by referencing them in the condition.

PR Overview

This PR is focused on debugging why copy results are not running after test failures. Key changes include:

• Modifying a test assertion in DynamicComposedChart.test.tsx.
• Updating the pipeline condition in build-npm-client-package.yml to only check if startTest is true.

Reviewed Changes

File	Description
packages/tools/devtools/devtools-view/src/test/DynamicComposedChart.test.tsx	Changes the test assertion which now contradicts itself by expecting the element to be both null and defined.
tools/pipelines/templates/build-npm-client-package.yml	Removes the succeededOrFailed() condition, which may prevent copying results when tests fail.

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

[dannimad]

https://dev.azure.com/fluidframework/public/_build/results?buildId=324912&view=ms.vss-test-web.build-test-results-tab shows a pipeline run in which jest tests failures are being show in the test tab.