Rerun filtered environments button

[omar-selo]

Resolves https://warthogs.atlassian.net/browse/RTW-307

Changes:

• Modify POST /v1/test-executions/reruns endpoint to take a set of test execution ids to rerun instead of just one
• Remove POST /v1/artefacts/<artefact-id>/reruns endpoint as I used the endpoint above instead. The reason is that this endpoint will have to filter exactly as the frontend does. This could be prone to errors, so instead I'd rather rerun exactly what the frontend user can see
• Add the button RerunFilteredEnvironments you can see how it works in the video below
• Replace filteredTestExecutionIds provider with filteredTestExecutions

Screencast.from.2024-05-09.13-34-33.webm

[andrejvelichkovski]

Overall looks good to me, but I have two small concerns

[andrejvelichkovski]

This way of checking whether the Test Execution ID is valid might lead us to the API behaving somewhat inconsistent. For example, if only one of the test execution IDs provided is invalid, then all test executions appearing before it would have been rerun, while the ones after it wont.

Maybe a better way we can handle this is to firstly filter just test executions whose id is in the set, and then create TestExecutionRerunRequest just for those? Or maybe just ignore the ones that have invalid ID, instead of raising the HTTPException

[omar-selo]

Good point. I opted to rerun everything that can be rerun. Then return a list of what was rerun. If nothing gets rerun then I return a status code of 404. If everything gets rerun then a status code of 200. And if some rerun and others don't then I return 207.

[andrejvelichkovski]

Thanks for addressing the issues! Looks good to me now!