feat: implement heatmap multiples

[dv-usama-ansari]

Closes #112

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 @dvdanielamoitzi
  • 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

• Fixed behavior of heatmaps when multiple categorical columns are selected

Screenshots

Additional notes for the reviewer(s)

• The performance of the component is noticeably slow when multiple categorical columns are selected for a medium-large dataset
• There are errors in the console which refer to incorrect attributes being set to <svg> elements during render
• The sorting of one of the axes of a heatmap also sort the other heatmaps in sync
• The labels do not have a good placement if multiple heatmaps are rendered

[dvmartinweigl]

Unfortunately this does not scale well in Bioinsight. Also there are not scrollbars if the matrix overflows.

[dvmartinweigl]

@dv-usama-ansari and me decided to limit the number of categorical columns to 2, as there is some misbehavior and bugs in the matrix approach. Also this does not scale well in our dashboard like applications.

We can keep this PR open and take another look at a later point.

[dv-usama-ansari]

@dv-usama-ansari and me decided to limit the number of categorical columns to 2, as there is some misbehavior and bugs in the matrix approach. Also this does not scale well in our dashboard like applications.

We can keep this PR open and take another look at a later point.

Please note that I have entered comments in the code to indicate this, we therefore do not need a separate PR