Centralization of Service Compatibility Patches and Refactoring of UTType Compatibility Handling

The impact of this change on WebView2Mac is mainly reflected in the modification of the underlying implementation of macOS service (such as clipboard, text services, etc.) type determination logic. Since WebView2Mac directly or indirectly inherits and reuses code related to remote_cocoa’s BridgedContentView and RenderWidgetHostViewCocoa, all service type determinations related to the NSServicesMenuRequestor protocol (such as validRequestorForSendType:returnType:) will now use the new UTType compatibility utility functions. In theory, this enhances compatibility with future macOS versions and reduces the risk of service failures caused by changes in type strings. The actual functional behavior should remain consistent with previous versions, but if downstream code depends on the details of the old type determination implementation, adaptation may be required. Overall, this change is an improvement in underlying compatibility and robustness, and will not affect the main workflow or performance of WebView2Mac, but it is recommended to pay close attention to regression testing of service-related features across both new and old macOS versions.