fix(smol): change abseil Windows patch to use linker flag

Change Windows duplicate symbol fix from disabling abseil.lib build
to using /FORCE:MULTIPLE linker flag. This is a more robust solution
that allows both libraries to be built properly.

Previous approach: Disabled abseil.lib build on Windows (type: 'none')
New approach: Add /FORCE:MULTIPLE to all Windows link operations

Rationale:
- /FORCE:MULTIPLE is the standard MSVC solution for duplicate symbols
- Allows abseil.lib to be built properly for all targets
- Linker picks one definition when symbols are identical
- Safer than preventing library build entirely

The duplicate symbols occur because v8_libbase includes abseil
implementations while abseil.lib also provides them. Both provide
identical implementations, so /FORCE:MULTIPLE is safe.

Author: jdalton

packages/node-smol-builder/patches/011-socketsecurity_fix_abseil_windows_duplicate_symbols_v24.10.0.patch

@@ -1,43 +1,38 @@
 # @node-versions: v24.10.0+
 # @description: Fix abseil duplicate symbol errors on Windows
 #
-# Disables standalone abseil.lib build on Windows by changing the abseil
-# target type from 'static_library' to 'none'. This prevents LNK2005
-# linker errors where absl::Mutex::Dtor and other symbols are defined
-# in both abseil.lib and v8_libbase.lib.
+# Adds /FORCE:MULTIPLE linker flag globally for Windows builds to allow
+# duplicate symbol definitions between abseil.lib and v8_libbase.lib.
 #
 # Root cause: Node.js v24 extracted abseil to a separate build target
 # (tools/v8_gypfiles/abseil.gyp) to share code between V8 and perfetto.
-# On Windows with MSVC, this creates duplicate symbol errors because
-# V8's libbase already includes the necessary abseil implementations.
+# v8_libbase depends on and links against abseil.lib, but some abseil
+# symbols end up defined in both libraries, causing LNK2005 errors when
+# linking executables that use both (like torque.exe).
 #
-# Solution: On Windows only, configure abseil as type 'none' so headers
-# are available but no separate static library is built. V8's libbase
-# continues to provide the abseil implementations it needs.
+# Solution: Add /FORCE:MULTIPLE to all Windows link operations via the
+# toolchain configuration. The linker will pick one definition of each
+# duplicate symbol. This is safe because the implementations are identical.
 #
-# Error: abseil.lib(abseil.mutex.obj) : error LNK2005: absl::Mutex::Dtor
-# already defined in v8_libbase.lib(v8_libbase.mutex.obj)
+# Original errors:
+# LNK2005: absl::Mutex::Dtor already defined in v8_libbase.lib
+# LNK1169: one or more multiply defined symbols found
 #
 # References:
 # - https://github.com/nodejs/node/pull/57289 (abseil extraction)
-# - https://github.com/nodejs/node/pull/57582 (abseil deadlock detection)
+# - https://learn.microsoft.com/en-us/cpp/build/reference/force-force-file-output
 
---- a/tools/v8_gypfiles/abseil.gyp
-+++ b/tools/v8_gypfiles/abseil.gyp
-@@ -3,7 +3,15 @@
-   'targets': [
-     {
-       'target_name': 'abseil',
--      'type': 'static_library',
-+      'conditions': [
-+        ['OS=="win"', {
-+          # On Windows, abseil symbols are already included in v8_libbase.
-+          # Building a separate abseil.lib causes LNK2005 duplicate symbol errors.
-+          'type': 'none',
-+        }, {
-+          'type': 'static_library',
-+        }],
-+      ],
-       'toolsets': ['host', 'target'],
-       'variables': {
-         'ABSEIL_ROOT': '../../deps/v8/third_party/abseil-cpp',
+--- a/tools/v8_gypfiles/toolchain.gypi
++++ b/tools/v8_gypfiles/toolchain.gypi
+@@ -525,6 +525,11 @@
+               '/bigobj', # Prevent C1128: number of sections exceeded object file format limit.
+             ],
+           },
++          'VCLinkerTool': {
++            'AdditionalOptions': [
++              '/FORCE:MULTIPLE', # Allow duplicate symbol definitions (abseil.lib vs v8_libbase.lib).
++            ],
++          },
+         },
+       }],
+       ['v8_target_arch=="ia32"', {