Expose mapping between rendered path nodes and SCKAN nodes

[napakalas]

Expose the mapping between a pathway’s rendered nodes in the map and their corresponding nodes in SCKAN. This is particularly relevant for cases involving aliases, simplified nodes, or abstracted pathway nodes.

This mapping will allow the sidebar UI to clearly show how SCKAN pathway nodes relate to what is actually rendered in the map, improving usability and transparency.

Proposed change
Update flatmap-maker to expose a new attribute, node-mappings, under pathways.
node-mappings should be a list of pairs:

• the rendered node(s) in the map
• their corresponding SCKAN node(s)

Example:

"node-mappings": [
  [["ILX:0793559", []], ["ILX:0793559", []]],
  [["UBERON:0002369", []], ["UBERON:0001235", ["UBERON:0002369"]]]
]

Motivation (why this is needed)
To support the planned sidebar UX, the UI must be able to:

1. Display a single list of SCKAN nodes as the primary listing
2. Use icons to indicate whether a term is a complete match, partial match, or removed
3. Provide hover details explaining why a feature is missing and which map alias replaced it
   To enable this, we need transparent mapping information between SCKAN nodes and rendered map nodes, including aliases and simplified nodes.

Plan to support this
Translation of node information from SCKAN to the map must be accessible through the CQ database.
Required updates (in order):

• map-maker: expose alias, proxy, and simplified nodes in pathways (via node-mappings)
• map-knowledge: update database schema and CompetencyDatabase.import_knowledge
• flatmap-server: update map knowledge loading and add an SQL query to the CQ database to retrieve translated nodes

[nickerso]

@napakalas is it possible to also include the reason for the mapping?

[napakalas]

Updated by adding Motivation and Plan.