Support incremental page object generation

Inizia esaminando il PR #243 collegato, quindi segui DefaultTranslatorRunner.write(), TranslatorTargetConfig.isUpToDate(...), DefaultTargetConfiguration e JsonCompilerConfig. Verifica che l'opzione CLI e la configurazione raggiungano il runner, che gli oggetti pagina aggiornati saltino getGeneratedCode(), che le destinazioni mancanti o meno recenti vengano rigenerate e che gli output aggregati continuino a includere ogni oggetto pagina.

Problem

When utam-java is consumed via the compiler plugin in a downstream project, every mvn invocation triggers an all-or-nothing rebuild of every page object. google-java-format dominates the cost, so iterative dev loops pay the full formatting bill even when only one .utam.json source has changed.

Proposal

Add an opt-in incremental mode to the compiler that skips generation for page objects whose generated .java artifacts are already newer than their source .utam.json. This preserves current default behavior while giving downstream consumers a large speedup on repeated builds.

Suggested shape

• A CLI flag (e.g. --incremental / -I) and matching JsonCompilerConfig parameter.
• A TranslatorTargetConfig.isUpToDate(...) hook so custom target configs can opt in.
• DefaultTargetConfiguration implements the check via per-page-object mtime comparison: regenerate iff any expected target is missing or older than the source.
• DefaultTranslatorRunner.write() consults the hook before invoking getGeneratedCode() (where the formatter runs) and skips per-PO writes for up-to-date page objects. Aggregate outputs (manifest, DI config) still include every PO.

Linked PR

#243