fix: use legacyPattern in type mapping validation to detect dash-stripped variable names

The legacyPattern variable (dash-stripped form of legacy variable name) was
computed but never used in CheckTypeMappingUsageAsync. The Contains check
only looked for the original hyphenated form, missing cases where COBOL
variables like WS-ACCOUNT-NUM appear as WSACCOUNTNUM in converted code.

Now checks for both forms, consistent with CheckSignatureUsageAsync above.
Resolves github-code-quality warning on PR #22.

Author: gkaleta

Chunking/Validation/ConversionValidator.cs

@@ -363,15 +363,16 @@ private Task<List<ConsistencyIssue>> CheckTypeMappingUsageAsync(
             // Check for legacy variable name usage in converted code
             var legacyPattern = mapping.LegacyVariable.Replace("-", "");
 
-            if (chunk.ConvertedCode.Contains(mapping.LegacyVariable, StringComparison.OrdinalIgnoreCase))
+            if (chunk.ConvertedCode.Contains(mapping.LegacyVariable, StringComparison.OrdinalIgnoreCase) ||
+                chunk.ConvertedCode.Contains(legacyPattern, StringComparison.OrdinalIgnoreCase))
             {
                 issues.Add(new ConsistencyIssue
                 {
                     IssueType = ConsistencyIssueType.VariableNameMismatch,
                     EntityName = mapping.LegacyVariable,
                     Expected = mapping.TargetFieldName,
                     Actual = mapping.LegacyVariable,
-                    Description = $"Found legacy variable name '{mapping.LegacyVariable}' " +
+                    Description = $"Found legacy variable name '{mapping.LegacyVariable}' (or pattern '{legacyPattern}') " +
                                  $"in converted code - should be '{mapping.TargetFieldName}'",
                     Severity = IssueSeverity.Warning,
                     CanAutoFix = true