Fix families pages for dict-based backend responses

[cheezyrock]

Motivation

• Backend responses for families were changed from positional arrays to objects/dicts and a frontend route had a typo, which caused the families pages and family-related autocomplete to break.

Description

• Corrected the frontend API client route from /get_filtered_familes to /get_filtered_families in Frontend/src/api/routes.js.
• Added parseFamilyRecord helpers to Frontend/src/pages/Families.js and Frontend/src/pages/FilteredFamilies.js to normalize records returned either as arrays or as objects with named fields, and updated table rendering to use the normalized fields.
• Updated Frontend/src/pages/ExploreSystems.js to build family autocomplete options from either array-shaped or object-shaped family records.
• Adjusted polynomial and field rendering inputs in FilteredFamilies to use the parsed object fields (model_coeffs / modelCoeffs and base_field_label / baseFieldLabel).

Testing

• Ran npm --prefix Frontend run build which completed successfully and produced a production build with warnings.
• Ran npm --prefix Frontend run lint which failed due to many pre-existing repository-wide lint issues unrelated to these specific changes.

---

Codex Task

[cheezyrock]

Merge conflict created issue where families page wouldn't display. Used Codex to analyze repository and fix the merge errors.