feat: axis disabling [DHIS2-21565]

[HendrikThePendric]

Implements DHIS2-21565

Description

This PR implements the following axis disabling features for pivot tables:

• Disabling Axis for Drag and Drop
• Disabling Axis in menu items
• Changing behaviour of the + button when an axis is disabled
• In the conditions modal, ensure the Add to filter and Hide are the only modal actions

Disabling happens for dimensions that are not aggregatable, and a dimension is classified as aggregatable when:

• Its dimensionType is one of:
  • PROGRAM_INDICATOR
  • STATUS
  • CATEGORY
  • CATEGORY_OPTION_GROUP_SET
  • ORGANISATION_UNIT_GROUP_SET
• OR its valueType is numeric:
  • NUMBER
  • UNIT_INTERVAL
  • PERCENTAGE
  • INTEGER
  • INTEGER_POSITIVE
  • INTEGER_NEGATIVE
  • INTEGER_ZERO_OR_POSITIVE
  • BOOLEAN
  • TRUE_ONLY

Multi select

When in multi-select mode we use the same logic as we do when dragging a single dimension, but we apply the check to all items. So this means that if one out of many items is "non-aggregatable" the axis is disabled.

DnD hooks and helpers

While working on the DraggableDimensionItem I found that the component was starting to get boated, so I created a hook to encapsulate the DnD logic. I found this to be quite a nice pattern so I decided to do it for the layout chip. Similarly, I needed to export a new helper from the DnD provider dir, and found some of the current helpers to be exported from a hook file, so I created a new dnd-data.ts file and moved the helpers there.

---

Quality checklist

• Dashboard tested N/A
• Cypress and/or Jest tests added/updated
• Docs added N/A
• d2-ci dependency replaced N/A

---

ToDo

• Confirm aggregatable dimension classification logic with @janhenrikoverland
• Confirm disabled axis drop target UI @cooper-joe

---

Screenshots

[dhis2-bot]

🚀 Deployed on https://pr-249.event-visualizer.netlify.dhis2.org

[cooper-joe]

I've pushed a commit for the styles, which are now applied to the inner .content rather than on the main .container.

cursor: not-allowed is not having an effect because there is no collision when hovering a disabled container. I think we may want to adjust that behaviour, but I'm leaving noting as an enhancement that we can do following this PR. I've also noted a few dragging styles that need adjustment, so I'll log them together.

So, design LGTM. Logic needs adjustment, as noted in Slack, we can discuss there.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
1.7% Duplication on New Code

See analysis details on SonarQube Cloud