fix: remove categories from catalog interface

[axel7083]

What does this PR do?

We need to clear out some old dependencies/requirements (we have some hardcoded recent category etc. which are not used), moreover categories where at the same level than Models and Recipe, removing for now.

We can re-introduce then later when we would have completed #447

Screenshot / video of UI

What issues does this PR fix or reference?

Fixes #461

How to test this PR?

• existing tests ensure no regression

[jeffmaury]

I don't understand the rationale for this. This is a change from the mockup and I don't remember being addressed during UI Call.
@slemeur @ekidneyrh WDYT ?

[axel7083]

I don't understand the rationale for this. This is a change from the mockup and I don't remember being addressed during UI Call. @slemeur @ekidneyrh WDYT ?

If you want to split the models and the recipes. What do we do with the categories ?

[jeffmaury]

I don't understand the rationale for this. This is a change from the mockup and I don't remember being addressed during UI Call. @slemeur @ekidneyrh WDYT ?

If you want to split the models and the recipes. What do we do with the categories ?

They are related to recipes (a way to group and display them)

[axel7083]

I don't understand the rationale for this. This is a change from the mockup and I don't remember being addressed during UI Call. @slemeur @ekidneyrh WDYT ?

If you want to split the models and the recipes. What do we do with the categories ?

They are related to recipes (a way to group and display them)

Okey got it. I will close this PR and include the change in #464