Inferno GUI improvments

Description

Inferno GUI is not user friendly. The following changes here aim to correct some bugs and clarify inferno usage.

• Add 2 filters on the first page: one for orbit type, the other for the orbit number #2534
• On the scenario selection page, only keep the scenario number 4 which groups area based on ROI #2535
• On the third page: be able to tune the processing depending of the group. Actually it is the same processing for all groups selected on page 2. #2536
• Reduce the "quicklook" size to get a compact layout
• Better support for the "Available" parameter on the column. This parameter indicates if the product is available "on-band" or on drive. Edit 1/12: when talking about it with Yannick, Philippe and Denis, EODag does not support it yet. There is an API call to transfer a product from band to disk and a a support in pygeodes

Definition of Ready

Generic:

• If this issue is consequent, it is split into subtasks with priority and complexity evaluated. These subtasks should be linked to this issue. (To do on GitLab interface after writing this issue)
• Issue complexity evaluated
• Priority of issue evaluated
• If there is specific test data needed, it should be detailed and available
• If there is a specific documentation/specification need, it should be available to the development team
• Time during the sprint to realize this issue
• Blocking elements resolved (check if non-applicable, detail otherwise the resolved elements)

Specific:

• Get access to https://gitlab.cnes.fr/inferno/inferno

Definition of Done

Generic:

• No test regression on CI
• Code reviewed by peers
• Code cleaned, no "debug" traces or "TODO" comments kept.
• New code documented