[investigation] MultiPathComponent to display by Key and by ID API endpoints

[gabriele-ct]

The component could be used to eliminate the second level by id, by key, etc. sections on the endpoint pages and instead display them in the individual tabs. For example look at this page.

Make sure that the content indexing it still working as expected

[nkuehn]

@basebander just in case that helps with the analysis of your problems:

• restrictions to the mutipath that's currently being built in case that helps: No headings inside them (impossible to get consistent highlighting of the current heading inside the index nav)
• not having certain subsections in the index nav is possible today (fourth / fifth level are visually the same towards the user as third but are not shown in the index nav. We have that in some pages with long lists.

[zbalek]

Hi @gabriele-ct, @basebander has now tested the use case outlined above using the new MultiPath component. And so there's a couple of things we've noticed:

• [x] The component does not work well on mobile atm, the tabs names don't wrap into a second line. (This will likely cause an issue for self-learning, and so I created a ticket for this fix: https://github.com/commercetools/learning-tech/issues/676 .)
• [x] - There seems to be a bit of a delay when clicking on different index entries. Is this something that the ET team could improve? I suppose this issue will become more prominent once we start rolling out the component more widely. [the issue was not cause by the component]

[basebander]

Hi everyone, in this draft PR, I've converted about 20 endpoints to find edge cases/bugs and have added my findings to the PR description. cc @zbalek