[Manohar Paturi (ManoharPaturi)]

Description

Fixes #4282

The attack class and converter filters and the two options endpoints now read both stored identifier layouts. The SDK falls back to children.attack for rows written before the nested structure existed and displays their type, and analytics already resolves the same fallback, so:

• filtering by an attack class now also matches the legacy spelling of the class name;
• converter filters check the legacy request converter list as well, and a row only counts as converter free when neither layout carries any, which keeps the empty list absence overload working for wrapped rows;
• both options queries (SQLite and Azure SQL) coalesce or union the two layouts, so the dropdowns offer the types the list displays.

Tests and Documentation

A regression in test_interface_attack_results.py, failing on main: a row stored with the legacy layout is found by its displayed attack class and its recorded converter, appears in both options lists, is kept by has_converters true, and stays out of has_converters false. The attack results, analytics metadata, and analytics suites pass (451 tests, apart from the preexisting operation id index case that fails identically on main). Ruff check and format are clean.

No documentation change needed, so I did not run JupyText.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.