Carry native encoder context through analysis replay

[FBartos]

Summary

This PR updates jaspTools as the orchestration layer for source-module analysis replay:

• keeps the existing runAnalysis(..., verbose = ...) controls for separating analysis diagnostics from Desktop/QML/native chatter
• stores the opaque jaspSyntax/SyntaxInterface column encoder context when a dataset is preloaded from a .jasp file or source dataset
• passes that context into decodeAnalysisResults() so result replay uses the dataset/QML provenance that produced the analysis
• removes the old preloaded column-mapping plumbing; jaspTools no longer performs or transports R-side decoding maps
• preserves jaspTools as a thin bridge: it resolves inputs, runs the analysis, and forwards the captured context to jaspSyntax/jaspBase

Why

Encoding and decoding should be invisible to module authors and test authors. The lower-level PRs make Desktop the source of truth for token replacement; jaspTools only needs to keep the captured context attached to replay so old .jasp files and source-module tests decode the same way JASP would.

Related PRs

• jasp-desktop native encoder context: Expose native column encoder context jasp-desktop#6249
• jaspSyntax encoder-context R API: Expose Desktop encoder context for result decoding jaspSyntax#8
• jaspBase result materialization/runtime replay: Support source-module wrapped analysis replay jaspBase#204

Validation

• focused jaspTools lifecycle tests passed: test-jaspSyntax-lifecycle.R (133 pass, 3 gated real-Descriptives skips)
• focused jaspBase tests passed: test-result-object-decoding.R, test-runWrappedAnalysis.R
• focused jaspSyntax tests passed against the rebuilt local Desktop bridge: test-desktop-jasp-contract.R, test-dataset-helpers.R
• R parse check passed
• git diff --check

[FBartos]

Closing this wrong-base duplicate. The jaspTools bridge PR targeting development is #79: #79