fix(guard): bypass std::invoke in tuple callable guards

Problem
- MSVC still failed on named tuple-bound guard macros after replacing std::apply.
- The remaining failure came from std::invoke during tuple-expanded callable guard invocation.

Implementation
- Changed the guard tuple expansion helper to call the predicate directly.
- Kept the tuple expansion path and guard semantics unchanged.

Tests
- Rebuilt with clang++ targeting x86_64-pc-windows-msvc.
- Ran the Guard.* test suite and related guard coverage successfully.

Notes
- Follow-up compatibility fix for MSVC.
- No API or behavior changes intended.

Author: sentomk

include/ptn/pattern/modifiers/guard.hpp

@@ -328,8 +328,8 @@ namespace ptn::pat::mod {
         Pred                   &&pred,
         Tuple                  &&tuple,
         std::index_sequence<I...>) {
-      return std::invoke(std::forward<Pred>(pred),
-                         std::get<I>(std::forward<Tuple>(tuple))...);
+      return std::forward<Pred>(pred)(
+          std::get<I>(std::forward<Tuple>(tuple))...);
     }
 
     template <typename Pred, typename Tuple>