Standardize Index (ordinal) vs hasTotalNumberOf (count) properties

[aro-max]

Problem

Some properties currently use *Number in ways that mix ordinal positions and total counts, which can cause ambiguity.
Example:

• episodeNumber may refer to the episode’s position in a season or the total number of episodes, depending on context.
  Similar inconsistencies exist for season, segment, line, and part numbering.

---

Proposed Solution

Semantic rules:

• …Index = position / ordinal (1-based)
• hasTotalNumberOf… = totals / quantities

Follow the pattern already used in the audio/video area hasTotalNumberOfAudioTracks

---

Properties

• ec:hasEpisodeIndex
• ec:hasEpisodeIndexInSeason
• ec:hasEpisodeIndexInSerial
• ec:hasEpisodeIndexInSeries
• ec:hasSeasonIndex
• ec:hasSegmentIndex
• ec:hasLineIndex
• ec:hasTotalNumberOfEpisodes
• ec:hasTotalNumberOfGroupMembers
• ec:hasTotalNumberOfParts
• Artefact/text line corner properties renamed from …LineNumber to …LineIndex