fix: use CSV header to resolve column indices dynamically

[Jah-yee]

Summary

The JavaScript code references CSV columns by fixed index (row[1] for language, row[4] for comments). If the CSV column order ever changes, filtering and sorting will silently break.

Fix

Replace hardcoded indexes with dynamic lookup from the CSV header row:

• Added colIdx object that maps column names to their index positions
• Language filter now uses row[colIdx.language] instead of row[1]
• Sort by comments now uses row[colIdx.comments] instead of row[4]
• Language aggregation in the filter population also uses colIdx.language

The CSV header is: repo,language,title,url,comments,labels,state

• language = index 1
• comments = index 4

The fix is backwards-compatible with the current column order.

Testing

• Single-file change (app/frontend/index.html)
• No functional changes to existing behavior — only resilience against future column reordering
• All references to row[N] that depended on column positions are updated

Fixes #108

[drkrillo]

Hey @Jah-yee ! Thanks for your interest in contributing.

Before reviewing the PR, make sure to follow its PR template. Also, make sure that you have read the CONTRIBUTING.md file and that you are alligned with it.

Thanks for undrestanding!