fix: apply EmptyCollectionIfNull to record constructor args (#943)

[wyf027]

Summary

• Apply EmptyCollectionIfNull (and other destination transforms) to record/class constructor arguments when null sources would otherwise skip transforms.
• Skip destination transforms when a member has an explicit .Map() resolver so explicit null mappings are preserved.

Fixes #943
Relates to #952 (ctor-parameter path; property path covered by #966)

Test plan

• NullableCtorPropagationCurrentWorkWithDestinationTransform (EmptyCollectionIfNull no longer initializes empty collections in reccords for nullable source #943)
• ExplicitNullMapping_ShouldNotBeOverridden_ByDefaultEmptyCollectionTransform (DestinationTransform.EmptyCollectionIfNull overrides explicit null mapping #952)
• CI green on development

[wyf027]

Heads-up for review: #943 ctor-path transforms were partially addressed upstream in #945 (development). This PR additionally wires ApplyDestinationTransform + explicit-map skip (HasExplicitMemberMap) on the ctor path — overlapping with #966 (#952) on the adapter path. The added regression test currently references #952 (explicit null vs EmptyCollectionIfNull), same scenario as #966; happy to rebase onto latest development and split/rename tests if that helps review.

[wyf027]

Consolidated into #966: ctor-path ApplyDestinationTransform + explicit-map skip now lives on fix/explicit-null-map-952-dev with record-ctor regression coverage in WhenPerformingDestinationTransforms. #943 baseline remains on development via #945.