[Quality Management] Do not show notification when inspections are not created

[JakovljevicDusan]

What & why

Do not show notifications when inspections are not created, for example due to setup that instructs to use existing inspections.

Linked work

Fixes AB#624741

[alexei-dobriansky]

Agentic PR Review - Round 1

Recommendation: Request Changes

What this PR does

This changes Quality Management inspection creation so reused inspections no longer trigger the single "Quality Inspection created" notification, and batch notification tracking only includes inspections where IsLastInspectionNewlyCreated() is true. The direct single-create path looks correctly guarded before NotifyInspectionCreated, and batch partial-creation cases should still notify for newly created inspection numbers only. However, this is a behavior change with no test coverage, and one multi-record creation path still appears to mix "found/reused" inspections with "created" inspection IDs/counts.

Suggestions

S1 - Add regression coverage for notification suppression
No test files were added or modified. Please add tests under src/Apps/W1/Quality Management/test/src/, likely near QltyTestsCreateInspect.Codeunit.al, that assert no send notification occurs when setup reuses an existing inspection, and that the notification still occurs when a new inspection is actually inserted.

S2 - Separate reused inspections from newly-created counts in multi-record paths
CreateInspectionForSelfOrDirectParent still increments InspectionCreatedCount and adds LastCreatedQltyInspectionHeader2."No." to CreatedQltyInspectionIds whenever CreateInspectionWithMultiVariants returns an inspection, even if it was reused. If this list feeds "created inspections" messages/display, separate "attempt succeeded/found an inspection" from "new inspection was inserted" using LocalQltyInspectionCreate.IsLastInspectionNewlyCreated() so reused records do not inflate created counts while still avoiding false failures.

Risk assessment and necessity

Risk: The touched paths are user-visible notification/display paths in QltyInspectionCreate.Codeunit.al and batch integrations in Assembly, Manufacturing, Receiving, and Warehouse; without tests, a regression could either reintroduce false "created" notifications or suppress real creation notifications.

Necessity: The fix is necessary for setups that intentionally reuse existing inspections, but it needs regression coverage and consistent created-vs-reused counting before merge.

---

[AI-PR-REVIEW] version=1 system=github pr=8555 round=1 by=alexei-dobriansky at=2026-06-10T15:48:34Z lastSha=5b9336664b2125efa6de142044e72df6afee3312 suggestions=S1,S2

[alexei-dobriansky]

@JakovljevicDusan, I guess we can ignore S1, please check S2.