test: component versions report in Cypress HTML report

[kithwa]

PR Checklist

• Unit Tests have been added for new changes
• API tests have been updated if applicable
• All commented code has been removed
• If you've added a dependency, you've ensured license is compatible with Apache 2.0 and clearly outlined the added dependency.

What are you changing?

• add versions of DMT components in the custom report

Anything the reviewer should know when reviewing this PR?

• the run result can be found in this link: https://github.com/device-management-toolkit/e2e-testing/actions/runs/24705326798

If the there are associated PRs in other repositories, please link them here (i.e. device-management-toolkit/repo#365 )

[madhavilosetty-intel]

@kithwa quick question on setupNodeEvents, the function updates config.env on lines 61 and 71, but doesn't return config at the end. From what I've read, Cypress only picks up changes to config when the updated object is returned; otherwise the changes get dropped for anything outside this function.

Have you seen the merged keys actually reach the test specs in CI? Just want to confirm whether this is working as intended, or if return config is missing.

Also, would it be possible to include sample-web-ui and rpc-go versions in the report as well? For sample-web-ui, I think we could read the version from package.json. What do you think?