ja: read intervals with a verb on each endpoint

[yasumorishima]

Follows #726 on the ja branch. Thanks @moritz-gross for the # audit-ignore pointer on #720 — this PR is the first one that needs it, and I have measured what it does (numbers at the end).

Why this rule cannot be translated slot by slot

ClearSpeak-intervals reads (c,d) as "the interval from c to d, not including c or d". Copying that shape into Japanese changes the meaning: English negation distributes over the disjunction, but Japanese または does not, so 「c または d を含まない」 asserts not(c) or not(d) rather than neither. The connectives and/or/but also cannot be chosen independently of polarity in Japanese.

So each endpoint now carries its own verb, joined by the continuative form:

	now reads
(c,d)	区間 c から d まで, c を含まず d を含まない
[c,d]	区間 c から d まで, c を含み d を含む
[c,d)	区間 c から d まで, c を含み d を含まない
(c,d]	区間 c から d まで, c を含まず d を含む

When one side is infinite there is only one clause, so the first verb switches to its terminal form (を含む / を含まない) instead of the continuative.

The range itself also had to move: から and まで are postpositions, so the endpoints come first, the same change as #726.

Machine-translation fixes in the same rule

• コメントはありません — this was the bare word "not" from then: [t: "not"], rendered as "there are no comments". It was spoken in every open interval.
• 含まれるもの ("things that are included") for "including".
• 間隔から for "the interval from". 間隔 is spacing or an interval of time, not a mathematical interval; that is 区間.

audit-translations

Measured on this branch against a detached checkout of ja at 544e7fb:

	Rule differences	Untranslated
ja baseline	28	3683
this branch, no marker	31	3683
this branch, with # audit-ignore	28	3674

So the marker cancels exactly the three intended differences.

One observation while using it, in case it is useful: # audit-ignore suppresses untranslated-text findings as well as rule differences (auditor.py lines 138 and 147), so marking this rule also hid its nine t: entries from the untranslated count. For a rule that diverges structurally but still needs its wording tracked, there is no way to silence only the structural half. I do not know whether that is worth a separate marker — happy to open an issue on the tool if you would like one.

I put the marker after name: rather than in the comment block above the rule, because build_raw_blocks splits on the item's first value line, so a leading - # comment can land in the previous rule's block.

Deliberately not in this PR

The non-ClearSpeak intervals rule in SharedRules/general.yaml has the same から … に shape, and additionally speaks translate(name(.),'-',' '), which reads the English tag name aloud in a Japanese voice. Fixing it needs interval terminology, and the obvious choice is not safe: [a,b) is called 右半開区間 by sources that name the open side and 左閉半開区間 by sources that name the closed side, so the same word can mean opposite things. The Japanese Wikipedia article uses the unambiguous two-sided forms 左閉右開 / 左開右閉 instead, which also map directly onto the tag names. I will send that separately.