API-CLI alignment of results

v1.15.0-beta: the batch and the service agree at the edges

What changed (atrium-project#72)

• The batch's LayoutReader method keeps an ALTO page without WIDTH/HEIGHT and a word without coordinates, as the service does. Before, it dropped them.
• A page that runs out of GPU memory even at the smallest LayoutReader window keeps the ALTO's own order, as in the service. Before, the batch skipped the page.
• The service reads its perplexity model from [CLASSIFY] MODEL_NAME in setup/config.txt, as the batch does; GPT2_MODEL_NAME still comes first. The shipped config names the same model as before (Qwen2.5-0.5B).
• The batch record's page quality_score is rounded to four decimals, as the service's.
• Both web frontends compute "Avg Quality" from Clear and Noisy lines only, as the API does.
• /info lists every line field (original_lang, orig_lang_score, page, page_label added); the spec's field descriptions are corrected.

Compatibility

• The API is unchanged apart from the version. Batch outputs now include lines and pages that were dropped before.

Upgrade notes

• Pin 1.15.0-beta. Changing [CLASSIFY] MODEL_NAME now changes the service's model too, unless GPT2_MODEL_NAME is set.

Images this release certifies (images.json, atrium-project#81):

• ghcr.io/ufal/atrium-ocr-postprocess:1.15.0-beta = sha256:7c4fb7eceda555a4e6d996e40ad93fd2250061c68fdfa542853c3925d029b88c
• ghcr.io/ufal/atrium-ocr-postprocess-api:1.15.0-beta = sha256:8090aace5db566ca6b24e3fa15a85912fe2423422869632c6d0eb0c0a5588ebc

Full Changelog: v1.14.0-beta...v1.15.0-beta