fix(react-api-client): filter out unknown modules in the /modules endpoint.

[vegano1]

Overview

The desktop app is blocked when it gets an unknown module in the GET /modules response, which happens when the user clicks on the Devices side panel in the desktop app. Since we query modules for all discovered robots, it can be confusing to know which robot the unknown module is connected to. There will sometimes be a lag between developing and supporting new modules in the desktop app. So instead of blocking the desktop app, we should filter out unknown modules in the GET /response.

Closes: RABR-316

Test Plan

• Connect an unknown module (plate reader) to a robot and make sure we no longer see the "invalid module" modal.
• Make sure we still handle known modules like before.

Changelog

• Use the select option of react UseQuery to filter out unknown modules

Review requests

Risk assessment

low

[brenthagen]

LGTM, guards us a bit against modules outside the type system

[sfoster1]

nice!