Refactor api tests for modular pipelines change

[ravi-kumar-pilla]

Description

Partially resolves #1899

Development notes

• Updated cypress tests as the menu now shows the inputs/outputs datasets for a focussed modular pipeline
• Update conftest fixtures with edges case pipeline scenarios mentioned in -
  • Fix modular pipelines breaking when collapsed.  #1651
  • While nesting namespace pipelines, intermediary datasets get exposed to top level of the viz #1814
• Updated REST API responses as the modular pipeline mapping changed

QA notes

• This PR is part of a bigger refactor (Refactor Namespace Pipelines  #1897) of modular pipelines and is created to ease review process.
• The CI build might fail as this PR is not self-sufficient

Checklist

• Read the contributing guidelines
• Opened this PR as a 'Draft Pull Request' if it is work-in-progress
• Updated the documentation to reflect the code changes
• Added new entries to the RELEASE.md file
• Added tests to cover my changes

[merelcht]

I see there's still a TODO here. The fixture is really large and quite hard to read IMO. Can we perhaps come up with example pipelines with more self-explanatory names and variable names? dataset_1 etc is a bit hard to follow.. Or at least can we add more explicit notes that explain what each of these use_cases are for?

[ravi-kumar-pilla]

Hi @merelcht , Yes even I felt the same. So for now kept a TODO and added links in the docstring of the fixture so the devs can take a look. I wanted to get some help from reviewers on how to do this more efficiently.

Based on your suggestion, I will try to come up with more meaningful names and see if we can split the fixture into multiple parts for each use case. Thank you

[merelcht]

This is a huge improvement! The test fixtures are much easier to understand now. Thanks @ravi-kumar-pilla ⭐ ⭐ ⭐ !