Use try/catch for non-blocking Java calls and log Cause

[EtaCassiopeia]

Summary

getProviderHooks and wrapJavaHook.before were wrapping Java SDK calls in ZIO.attempt(...).catchAll(...). ZIO.attempt creates a Sync node and catchAll adds a FlatMap node — two ZIO instances the runloop must interpret. Since the wrapped calls are non-blocking, in-memory Java methods, a plain try/catch + Exit.succeed (or ZIO.succeed { try { ... } catch ... }) achieves the same safety with fewer runloop iterations.

Also upgrades getProviderHooks error logging from ZIO.logWarning(s"... ${e.getMessage}") to ZIO.logWarningCause(...) so the full Cause (with stack trace) appears in diagnostics.

Changes

• FeatureFlagsLive.getProviderHooks — ZIO.attempt + catchAll → try/catch + Exit.succeed; log Cause.fail(e) instead of just the message
• FeatureFlagsLive.wrapJavaHook.before — ZIO.attempt + catchAll(_ => ZIO.none) → ZIO.succeed { try { ... } catch { case NonFatal(_) => None } }

Both call sites assume NonFatal (preserves original Exception-catching behavior; VirtualMachineError/LinkageError propagate).

Credit

Spotted in #110 by @guizmaii. The logWarningCause upgrade is an addition; the original PR kept the message-only logging.

[EtaCassiopeia]

Tested independently; closing in favor of #110.