Add trace logging to crypto-trading aggregate handlers

[Copilot]

Add info-level logging to all @CommandHandler and @EventHandler methods in crypto-trading aggregates to enable message flow tracing.

Changes

• Account.java: Added logger and logging to command handler
• Wallet.java: Added logger and logging to 6 command handlers + 1 event handler (wallet lifecycle, balance operations, reservations)
• CryptoMarket.java: Added logger and logging to 2 command handlers (market creation, order placement/execution)
• OrderProcessManager.java: Added logger and logging to 3 command handlers + 6 event/bridge handlers (order process orchestration)

Example

@CommandHandler(produces = WalletCreditedEvent.class, errors = {...})
public Stream<DomainEvent> credit(@NotNull CreditWalletCommand cmd, @NotNull WalletStateV2 currentState) {
    log.info("CommandHandler: Crediting wallet for walletId={}, currency={}, amount={}", 
        cmd.id(), cmd.currency(), cmd.amount());
    // ... existing logic
}

@EventHandler(produces = BuyOrderPlacedEvent.class, errors = {})
public Stream<DomainEvent> handle(AmountReservedEvent event, OrderProcessManagerState state) {
    log.info("EventHandler: Amount reserved for userId={}, currency={}, amount={}, referenceId={}", 
        event.userId(), event.currency(), event.amount(), event.referenceId());
    // ... existing logic
}

Each log includes handler type prefix and relevant contextual data (IDs, amounts, currencies, references) for effective tracing. @EventSourcingHandler methods remain unchanged as they handle state reconstruction, not business flow.

Original prompt

in the crypto-trading test app, add info log statements in all the @eventhandler and @CommandHandler annotated methods of all the Aggregate (classes that implement the Aggregate interface). Add enough context to the log messages so it's easy to trace the message flow

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.