[transferwebhooks] Code generation: update services and models

[AdyenAutomationBot]

This PR contains the automated changes for the transferwebhooks service.

The commit history of this PR reflects the adyen-openapi commits that have been applied.

[gemini-code-assist]

Code Review

This pull request updates several webhook models to support unknown enum values during deserialization and simplifies property assignments by removing redundant value accessors. However, the reviewer identified several critical issues: the new enum conversion logic introduces a risk of NullReferenceException by accessing properties on potentially null objects across multiple files. Additionally, the updated polymorphic deserialization logic in classes like BankAccountV3AccountIdentification is flagged for being inefficient and for logically contradicting the goal of supporting unknown enums. Feedback also suggests implementing more robust null handling when casting raw JSON strings to enum types to avoid creating invalid enum instances.

[gemini-code-assist]

The implicit conversion to string? will throw a NullReferenceException if value is null. While the previous implementation safely returned null, the new code attempts to access value.Value without a null check. This is a critical issue as it can cause crashes during serialization or whenever an enum property is accessed as a string. This pattern is repeated across almost all model files updated in this PR.

                if (value == TypeEnum.AuLocal)
                    return "auLocal";
                
                return value?.Value;

[gemini-code-assist]

The implicit conversion to string? will throw a NullReferenceException if value is null. This critical bug should be addressed here and in all other model files following this pattern.

                if (value == AmountAdjustmentTypeEnum.ForexMarkup)
                    return "forexMarkup";
                
                return value?.Value;

[gemini-code-assist]

The implicit conversion to string? will throw a NullReferenceException if value is null. This critical bug affects multiple enums in this file, including CategoryEnum, StatusEnum, DirectionEnum, ReasonEnum, and TypeEnum.

                if (value == CategoryEnum.TopUp)
                    return "topUp";
                
                return value?.Value;

[gemini-code-assist]

The polymorphic deserialization logic here has two significant issues:

1. Efficiency: For every variant, it performs a null check, an implicit string conversion, and a FromStringOrDefault lookup. This is repeated up to 16 times per object. A more efficient approach would be to extract the type property from the JSON once and use it to select the correct model.
2. Logic Contradiction: The check FromStringOrDefault(...) != null ensures that only known enum values are accepted for each variant. However, the individual models (like AULocalAccountIdentification) were updated in this PR to support unknown enum values. This wrapper effectively negates that change for polymorphic types, as it will throw a JsonException if the type string is not recognized by any variant, even if one of the models could have handled it as an unknown enum value.

[gemini-code-assist]

When typeRawValue is null (e.g., if the JSON property is explicitly set to null), the expression (AULocalAccountIdentification.TypeEnum)typeRawValue might create an 'empty' enum instance instead of returning a null reference, depending on how the explicit cast is implemented. It is safer to explicitly handle the null case to ensure the property remains null when the input is null.

                            type = new Option<AULocalAccountIdentification.TypeEnum?>(typeRawValue == null ? null : (AULocalAccountIdentification.TypeEnum.FromStringOrDefault(typeRawValue) ?? (AULocalAccountIdentification.TypeEnum)typeRawValue));