feat: support per-technique filtering of custom context menu items (#92)

[workmcg]

Closes #92

What this does

Adds an optional limit_techniques filter to custom context menu items defined in assets/config.json. Today every custom context menu option is applied to every technique in a layer; this lets an option be scoped to specific techniques.

{
  "label": "foo",
  "url": "https://test.com",
  "limit_techniques": ["T1098", { "id": "T1059", "tactic": "execution" }]
}

Design note - multi-tactic techniques

@rjsmitre raised on the issue that for multi-tactic techniques we need a way to say whether an entry applies to all instances of the technique or only some.

Rather than invent new semantics, this follows the pattern the layer format already uses for exactly this ambiguity. Technique objects in a layer file take an optional tactic field, and the spec states that if the field is not present, the annotations apply under every tactic the technique belongs to.

limit_techniques mirrors that:

• a bare ATT&CK ID ("T1059") applies to that technique under any tactic it appears in
• an { id, tactic } pair scopes the entry to that technique under one tactic, with tactic in shortname/phase-name form, matching the layer format's tactic field
• the two forms can be mixed in one list

This keeps the simple case simple and stays consistent with vocabulary contributors already know from layer files.

Backward compatibility

No breaking changes. limit_techniques is optional; when it is absent or an empty array, appliesTo() returns true and behaviour is identical to today - the item applies to every technique.

Changes

• context-menu-item.ts - adds the ContextMenuTechniqueFilter type, stores limit_techniques, and adds appliesTo(technique, tactic)
• context-menu-item.spec.ts - 7 unit tests covering: unset filter, empty filter, bare-ID match across tactics, bare-ID non-match, { id, tactic } scoped match, scoped non-match, and a mixed list
• config parsing - reads limit_techniques from custom_context_menu_items
• context menu rendering - filters items through applicableContextMenuItems
• docs - documents the new field

Testing

npm test in nav-app. The new specs cover the filter semantics directly; existing specs confirm the default path is unchanged.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud