Add possibility to specify which vis types to show in the sidebar

[dvdanielamoitzi]

We have the requirement to hide the heatmap in the general purpose vis. This PR introduces a property "visTypes" for the component which enables the developer to specify which vis types to show as options in the sidebar. If not specified, all vis types will be used.

Developer Checklist (Definition of Done)

Issue

• All acceptance criteria from the issue are met
• Tested in latest Chrome/Firefox

UI/UX/Vis

• Requires UI/UX/Vis review
  • Reviewer(s) are notified (tag assignees)
  • Review has occurred (link to notes)
  • Feedback is included in this PR
  • Reviewer(s) approve of concept and design

Code

• Branch is up-to-date with the branch to be merged with, i.e., develop
• Code is cleaned up and formatted
• Unit tests are written (frontend/backend if applicable)
• Integration tests are written (if applicable)

PR

• Descriptive title for this pull request is provided (will be used for release notes later)
• Reviewer and assignees are defined
• Add type label (e.g., bug, feature) to this pull request
• Add release label (e.g., release: minor) to this PR following semver
• The PR is connected to the corresponding issue (via Closes #...)
• Summary of changes is written

Summary of changes

• added visTypes prop to Vis component
• filtering by visTypes when registering the vis types

Screenshots

In this example I have only passed visTypes={[ESupportedPlotlyVis.HEATMAP]} to the Vis component, and as you can see there are no more options in the sidebar:

Additional notes for the reviewer(s)

• I'm not entirely sure if this is the way we want to do it, there would be the possibility to exclude certain vis types which might be better as newly introduced vis types would then show up by default whereas in my current approach the developer would need to add the new vistype to the visTypes props manually.

Thanks for creating this pull request 🤗

[dvmoritzschoefl]

this will kill performance of the app if visTypes is not memoized, since its wrapped in a context
should we do a shallow compare here? or alternatively we could call it initialVisTypes to make it clear that it will only affect the vis types at the first render, similiar to mantine-react-table (initialState) and other libraries

EDIT: the visprovider can handle this already by checking which vis are already in the provider