Connector categories: https://docs.google.com/spreadsheets/d/1JEUw4a4_K0PJswK8rVEntwRAY20lrdxp_aMPNjp54UQ/edit?usp=sharing

The current most popular design direction for the connector type selection page is to introduce a side-panel containing high-level categories. The intent is to better represent the variety and amount of connector types available in the catalog and also provide the user more options to filter down the available connector types quickly.

Here is the current iteration of this design just as a visual to help further explain what's needed:

Ideally we still want to use paginated API responses to support this view, as even though there's no pagination controls in the new design, the intent is to fetch additional pages as the user scrolls down. This will mean the initial request that the UI makes will not have all of the categories available to build the entire list, and would not have all the connector types available to calculate the number of connector types per category.

The API response for listing connector types would need to provide these categories in some form, and also provide the count of types per category in the API response. This should be calculated with any filter criteria applied, so if the user makes a search by name or label, the returned categories and how many connector types per category should reflect the number of filter results.

One other feature that we want for this view is to introduce the idea of "featured" connectors, and we'd like to have a default sort by "featured" and a secondary sort by name. So we'll need to identify what field or label would drive this "featured" category and ensure that the API can support sorting by this field.

I think that we should pass the category names through the UI's i18n layer, so it'd be okay to use snake-case or camel case for the category names in the API response, we just need to ensure that there's a 1:1 mapping that's obvious and will be easy to follow in the future.