Rewrite prefix generation and replacement logic

[kmcginnes]

Description

• Add splitIri, generatePrefix, and commonPrefixes utility modules
• Add PrefixLookup class for fast Map-based prefix lookups
• Rewrite generatePrefixes to use splitIri and generatePrefix
• Rewrite replacePrefixes to use PrefixLookup and splitIri
• Change usePrefixes/prefixesAtom to return PrefixLookup
• Remove __matches from PrefixTypeConfig
• Simplify saveConfigurationToFile and useImportConnectionFile
• Ensure generated prefix names are unique by appending a numeral on collision (e.g. soccer, soccer2, soccer3)
• Generate prefixes from vertex and edge IDs, not just types and attribute names
• Validate IRI local values against RDF rules, rejecting values with invalid characters (spaces, angle brackets, curly braces, pipes, carets, backticks, backslashes)
• Add backward compatibility tests for legacy __matches data

Validation

• All existing tests pass
• New unit tests cover splitIri, generatePrefix, PrefixLookup, commonPrefixes, prefix uniqueness, entity ID prefix generation, local value validation, and backward compatibility with legacy data

Prefix generation examples:

Rule	IRI	Prefix
Single path segment	http://www.example.com/soccer/ontology/League	soccer
Host fallback (no meaningful segments)	http://www.schema.org/City	schema
Skips resource segment	http://data.nobelprize.org/resource/country/France	country
Skips class segment	https://dbpedia.org/class/yago/Record106647206	yago
Skips numeric-only segments	http://example.org/2024/01/schema#Thing	schema
Multi-segment: first word + abbreviation	http://kelvinlawrence.net/air-routes/datatypeProperty/name	airdp
Multi-segment: camelCase abbreviation	http://kelvinlawrence.net/air-routes/objectProperty/route	airop
Special characters stripped (first word)	http://example.org/my-special_ns.v2/Item	my
Collision avoidance (1st namespace)	http://www.example.com/soccer/ontology/League	soccer
Collision avoidance (2nd namespace)	http://www.example.com/soccer/resource#EPL	soccer2
Collision avoidance (3rd namespace)	http://www.example.com/soccer/class#Team	soccer3

Local value validation (accepted):
my_item, my-item, v2.0, caf%C3%A9, café, item·1

Local value validation (rejected → no prefix generated):
my item, a<b, a{b}, a|b, a^b, a`b, a\b

Related Issues

• Fixes SPARQL namespaces seem to be reused #258

Check List

• I confirm that my contribution is made under the terms of the Apache 2.0
  license.
• I have run pnpm checks to ensure code compiles and meets standards.
• I have run pnpm test to check if all tests are passing.
• I have covered new added functionality with unit tests if necessary.
• I have added an entry in the Changelog.md.

[kmcginnes]

• Add de-duplication logic at the generatePrefixes level
• Add logic to ensure the splitIri logic rejects invalid local values

[codecov]

Codecov Report

❌ Patch coverage is 97.03704% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 64.90%. Comparing base (c5affc5) to head (c3d0849).
⚠️ Report is 77 commits behind head on main.

Files with missing lines	Patch %	Lines
...es/graph-explorer/src/core/StateProvider/schema.ts	92.85%	1 Missing ⚠️
...ges/graph-explorer/src/utils/rdf/generatePrefix.ts	97.36%	1 Missing ⚠️
...s/graph-explorer/src/utils/rdf/generatePrefixes.ts	96.29%	1 Missing ⚠️
packages/graph-explorer/src/utils/rdf/splitIri.ts	96.15%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #1539       +/-   ##
===========================================
+ Coverage   47.81%   64.90%   +17.09%     
===========================================
  Files         382      369       -13     
  Lines        8525     8327      -198     
  Branches     3159     3101       -58     
===========================================
+ Hits         4076     5405     +1329     
+ Misses       3070     2075      -995     
+ Partials     1379      847      -532     

Flag	Coverage Δ
unittests	64.90% <97.03%> (+17.09%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[arseny-kostenko]

I think this entire function can be summarized as:

return sanitizePrefix(
  splitSegmentIntoWords(segment)
    .map(w => w.charAt(0))
    .join("")
)

imho, it's easier to reason about it if it's written this way, because these two returns don't look the same semantically. Makes me even question — do we not sanitizePrefix if more than one word?

[kmcginnes]

@arseny-kostenko im running through some algorithm changes. Apparently prefixes are allowed to have hyphens, periods, and underscores. This changes how I would want to approach prefix generation. So I'm going through the changes now. Sorry for the whiplash.