feat: Update Explorer to support index by feature_id

[kaloster]

This is part of GeneExpression disambiguation efforts: chanzuckerberg/single-cell-data-portal#7456

Updates:

• This will always use schema.annotations.var.index as the column for geneIds
• If feature_name is available - it will use it as the column for geneNames - if not it will just default to varIndex
• Updated Gene, QuickGene and GeneSet to use a gene object { id: , name: } instead of a string to be able to utilize gene.id as the unique identifier
• This should work with datasets that are indexed with feature_name as the var.index (pre 6.0 migration) or indexed with name_0 (feature_id) as the var.index - post 6.0 schema.

Testing

• Tested against the example datasets (pre 6.0 migration)
• Tested against a newly indexed dataset (post 6.0 migration)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 0.00%. Comparing base (863c8f5) to head (ebeeeb9).
Report is 1 commits behind head on main.

Additional details and impacted files

@@     Coverage Diff      @@
##   main   #1222   +/-   ##
============================
============================

☔ 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.

[tihuan]

LGTM 🎉 Thank you so much for updating this, @kaloster 🤩 🙏

[tihuan]

@kaloster Does this mean I can merge the delimiter PR too 👀 ?

chanzuckerberg/single-cell-data-portal#7610

Thank you!

[kaloster]

@kaloster Does this mean I can merge the delimiter PR too 👀 ?

chanzuckerberg/single-cell-data-portal#7610

Thank you!

I think we'd have to wait until 6.0 schema migration is complete for this one