Validate explore column editor fields

[nsdeschenes]

Summary

• validate span sample table columns with the spans tab validator
• add valid validator fields to the column editor typed attribute maps
• remove invalid validated fields from the editor and query params so they stop rendering in the table
• add focused coverage for validation sanitization and typed modal selections

Test plan

• pnpm test-ci static/app/views/explore/tables/index.spec.tsx
• pnpm test-ci static/app/views/explore/tables/columnEditorModal.spec.tsx
• pnpm test-ci static/app/views/explore/spans/hooks/useValidateSpansTab.spec.tsx
• pnpm run lint:js static/app/views/explore/tables/index.tsx static/app/views/explore/tables/index.spec.tsx static/app/views/explore/tables/columnEditorModal.spec.tsx
• .venv/bin/prek run -q

[linear-code]

EXP-1030

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 7bc6137. Configure here.}

[cursor]

Invalid columns persist when lengths match

Low Severity

The effect that syncs query fields with validation only runs when validatedFields is shorter than fields. If an invalid column is dropped but the remaining list has the same length (e.g. duplicate valid columns plus one invalid name), setFields never runs and the invalid column can stay in the URL and span samples table.

 

^{Reviewed by Cursor Bugbot for commit 7bc6137. Configure here.}