Handling KEGG Prefixes with Identical URI Resolution

Nessuno ha ancora preso questa issue.

### KEGG Ontology Prefix Handling

We are currently using two KEGG prefixes:
- **kegg.reaction** ([KEGG Reaction](https://bioregistry.io/registry/kegg.reaction))
- **kegg.pathway** ([KEGG Pathway](https://bioregistry.io/registry/kegg.pathway))

Both of these prefixes resolve to the same base URL: `https://www.kegg.jp/entry`. For example:
- [R00100](https://www.kegg.jp/entry/R00100)
- [rsk00410](https://www.kegg.jp/entry/rsk00410)

I have been manually editing the `prefix.csv` files in my semsql installation to handle prefixes that are not already defined for ontologies we are currently developing. However, I'm uncertain how best to handle the KEGG prefixes given their shared resolution.

Any suggestions or guidance on a robust solution for this issue would be greatly appreciated.

Inizia esaminando i file prefix.csv e la gestione della risoluzione dei prefissi nell’installazione di semsql. Determina come kegg.reaction e kegg.pathway debbano rimanere distinti pur condividendo https://www.kegg.jp/entry, quindi verifica che entrambi i prefissi vengano risolti correttamente senza modifiche manuali.

Scritto dal modello di indicizzazione a partire dal testo della issue.