[CSR-2066] feat: added full test suite generation for convert command

[miguelangaranocurrents]

Description

Provide a brief description of the changes in this PR. Important to list all the changes made in overall. Describe any improvements, follow up tasks or edge cases related to this PR

This PR add the fullTestSuite.json file generation to the convert command.
It also allows generating multiple groups for the full test suite by accepting multiple files as different test groups.

PR Checklist

• I performed manual tests or added tests that prove my fix is effective or that my feature works.
• I have performed a self-review of my code.
• I have annotated my PR with comments, particularly in hard-to-understand areas.
• I have considered the security implications of this work.

Release Plan

Do we need to update any environment variables? Is there any order of releases required?

• Package release

Demo

Add screenshots or videos demonstrating the solution if applicable

https://www.loom.com/share/02ef05e48df64832a7cb884c960db874?sid=60ea25b0-e032-4e73-b888-1d0b0dffe6c3

Manual Testing

Describe in steps (support it with images if needed) how to try the changes of this PR. (Even the start/setup of the services needed to try it out). If it's a bug also include reproduction steps

1. Use the convert command to create instance files and the fullTestSuite JSON file
2. Use multiple JUnit XML files for having multiple groups
3. Use the upload command

[notion-workspace]

🆕 Move full test suite creation to convert

[vCaisim]

Hey Miguel, there is a little more work to be done here.

While testing I noticed a bug: if the groups contain the same spec names, the new created instances will overwrite the old ones and only the last group instances will be in the report directory. Check the video

Screencast.from.2025-02-06.10-42-17.mp4

[miguelangaranocurrents]

@vCaisim ready now, I fixed the bug of the same name instances being overwritten.

[vCaisim]

Tested, the issue is solved. Please address the latest feedback and update the option description for the --input-file so it is clear that it can accept multiple paths

[vCaisim]

• getParsedXMLInput, don't trim 2 times, use a variable
• it returns undefined if XMLString is emtpy string or parsedXMLInput is falsy value and getParsedXMLArray ends up with [undefined]

[miguelangaranocurrents]

The first point is done.
The second point:
I'm applying a .filter(Boolean); to the array after it is finished to remove the possible undefined elements. This is in line 14 of the same file.

[miguelangaranocurrents]

--input-file

Thanks for the feedback. Everything is addressed now :)