The USFM parser should trap the Trace warnings from VerseRef

[pmachapman]

These are warnings such as:

• "Just failed to parse a verse number: Sara"
• "Just failed to parse a chapter number: 5."

Which are emitted via Trace.TraceWarning.

They should be trapped then emitted via the warnings in the Serval build's execution data.

[ddaspit]

We need to check if this provides warnings that we cannot get from the validation status enum.

[pmachapman]

I ran a test with the following USFM:

\c 1.
\v v1
...

and the following warnings were reported when I trapped the trace warnings:

warnings: [
  "USFM Parsing error: Just failed to parse a chapter number: 1.",
  "USFM Parsing error: Just failed to parse a verse number: v1",
  "USFM versification error in project TEA, expected verse “MAN 1:15”, actual verse “MAN -1:15”, mismatch type MissingChapter (parallel corpus 6982813a9f64e57bf1d6f530, monolingual corpus 6982813a9f64e57bf1d6f52c)",
  "Only 7 segments were selected for training."
]