Optimize codegen for generated dependency property setters

[Sergio0694]

This pull request introduces an optimization to the DependencyPropertyGenerator by leveraging specialized XamlBindingHelper.SetPropertyFrom* methods for supported property types. This results in more efficient generated code for property setters, while maintaining compatibility with user-defined callbacks and fallback logic for unsupported types. The changes also refactor and extend the generator’s internal APIs to support this feature.

Optimized setter generation using XamlBindingHelper:

• The generator now detects if a property type supports a specialized XamlBindingHelper.SetPropertyFrom* method (e.g., SetPropertyFromBoolean, SetPropertyFromInt32). If so, it emits a direct call to this method in the generated setter for improved performance. This optimization is skipped if the property type is object or if the user has implemented a custom On<PropertyName>Set(ref object) callback. [1] [2] [3] [4]

API and model extensions to support the optimization:

• Added a new XamlBindingHelperSetMethodName property to the DependencyPropertyInfo record, and updated the generator pipeline to compute and pass this value. This enables the code generation logic to conditionally emit the optimized setter code. [1] [2] [3]

Well-known type name utilities:

• Introduced a utility method XamlBindingHelper(bool useWindowsUIXaml) in WellKnownTypeNames.cs to resolve the fully qualified type name for XamlBindingHelper, supporting both Windows and Microsoft UI XAML namespaces.

Code generation logic updates:

• Modified the setter and partial method generation logic to use the optimized path when available, and to only emit the boxed On<PropertyName>Set(ref object) partial method when the optimization is not used. [1] [2] [3] [4] [5]

These changes improve the efficiency of generated dependency property code and maintain backward compatibility for advanced scenarios.