Translation memory correctness fixes, job-creation validation, clearer error reporting, and a log-noise fix.

What's fixed

• Translation memory correctness. Approved translation memory could silently revert to pending when shared source text was re-translated by another node, and editing a single value on a node deleted translation memory for every other property on that node. Node approval also failed to promote memory for shared text owned by a different node's reference.
• Job creation validation. The choose-provider step in job creation didn't validate connector selection before enabling Next, so clicking Next while the connector was still resolving (e.g. a set with no default connector) could save a job with no provider set.
• Clearer job-check errors. Checking a job manually could show two notifications — a generic one and a warning that lost the actual server-side detail. Now a single warning uses the real error title/detail from the API, and the same error is also shown as a persistent box on the job page until a successful check or navigation away.
• Log noise. Benign "no translation set applies to this save" cases (invariant doctypes, culture-only saves) no longer log at warning level, and dirty-culture scanning is skipped for doctypes that don't vary by culture.

Other

• Build: update connector dependency versions (Microsoft, Jumoo.TranslationManager.AI)

Published to NuGet.