TT-7380, TT-7298 more mark verses changes

[nabalone]

More Mark Verses changes.

What changed

Verse-letter subparts (1:1a, 1:2b) are now first-class throughout Mark Verses validation and renumbering — this is the bulk of the work:

• Reference comparisons in markVersesEditReference.ts are now subpart-aware rather than whole-verse. Overlap detection, skip-ahead detection, and "in passage" checks all order at subpart granularity, so 1:2a and 1:2b no longer collide while the whole verse 1:2 still overlaps either.
• Passage bounds are read from the passage's reference string (which preserves the subpart, e.g. 1:1-1:3a) instead of the calculated startVerse/endVerse attributes (which strip it), so a bound ending at 1:3a is judged consistently against any other subpart.
• Skipped-verse detection now catches skipped leading subparts — e.g. 1:1 -> 1:2b flags the missing 1:2a, honoring both a passage that itself begins mid-verse and a prior row that already covered earlier subparts.
• Auto-renumbering continues split verses correctly. New markVersesRenumberLeadingRef decides what leads the following row after an edit: an end at part a continues at b, an a-inclusive range continues with the next letter, and a mid-verse single-verse range moves on to the next verse.
• Fixed the 1:1a-a case and the skipped-leading-subpart flag (1:1 -> 1:2b).

Inline editing + Edit Reference button in the table (new MarkVersesTable.tsx):

• The table was extracted into its own MarkVersesTable component.
• Click a reference to type it directly; Enter commits, Escape cancels.
• An Edit Reference button appears on the current (highlighted) row, opening the dialog beside the segment being worked on.
• Dedicated fixed-width warning and action columns keep reference text from shifting.
• Tapping a row's warning icon shows a tooltip explaining the flag.
• Extra scroll padding below the last row so it clears the floating Discussions button.

Feedback + housekeeping:

• A toast now warns when an applied edit (from either the dialog or inline editing) results in an error or warning reference.
• Dropped the IsMobile suffix from these files/components — they're used on desktop too now.
• Reverted the earlier "split-verse suffix beside the verse field" layout in EditReferenceDropdown.tsx (doesn't fit on Iphone SE, needs UX re-design. Keeping pre-existing implementation for now.
• Preserve segment splits when user switches to or from mobile mode
• Use "primary" theme to highlight the Play/Pause button, rather than a blue circle

🤖 Generated with Claude Code

[nabalone]

See Edit button:

Toast:

[nabalone]

Also, when the Play button is highlighted, I made it use the theme styling instead of the blue circle

[nabalone]

highlightAutoSegment is currently never set.

Claude says:
When is the auto-segment button highlighted in real use?
Today: never. No code passes highlightAutoSegment={true} to WSAudioPlayer. The prop is dead plumbing — it exists on WSAudioPlayer and WSAudioPlayerSegment but nothing sets it, so the auto-segment button always renders in its plain (non-highlighted) state. That's why I had to force it to show you.

Where it came from (git history): It was added in commit 3ff5d28 (TT-6814, the Phrase Back Translation mobile feature). The original caller highlighted the button under exactly this condition:

highlightAutoSegment={
isPhraseBackTranslation &&
mobileView &&
activityRef.current === Activity.Segment
}
So in real use it was meant to fire in the Phrase Back Translation (PBT) tool, on mobile, while the user was on the "Segment" activity — a guided cue nudging the user to tap Auto Segment.

That caller was then removed in 8fc598c (TT-7104, "reverting unstable mobile changes to PBT") and 2dc5f20 ("remove unused code"), which stripped the mobile PBT flow but left the highlightAutoSegment prop threaded through both components. It's now orphaned.