Simplify action/allAction error handling; drop wrapper-level logging

This patch focuses on simplifying error handling in the action and allAction wrappers. Errors from action implementations now propagate directly without wrapper-level extraction or re-logging of structured details. Tests were updated to reflect the new behavior. The prerelease is promoted to a stable 4.4.83.

Improvements

• Simplified action wrapper error handling (eb08305):

  • Removed the wrapper's try/catch path that inspected and re-logged errors with fields like message, name, code, stack, constraint, detail, and Sequelize validation errors.
  • The wrapper continues to validate that an action key exists and that the target item can be fetched before delegating to the action method. Failures now surface from the underlying action method without wrapper-enriched logs.
  • Impact: If you previously relied on the wrapper-emitted structured error logs (e.g., parsing database constraint names or Sequelize validation details from the wrapper logs), move that logging to your action implementation or to your call site.

• Simplified allAction wrapper error handling (eb08305):

  • Removed the wrapper’s error extraction and re-logging logic for allAction invocations (including database constraint and Sequelize validation detail extraction).
  • The wrapper still validates the existence of the requested allAction and delegates invocation; errors propagate from the underlying implementation.
  • Impact: Adjust any monitoring or alerting that expected those wrapper-level structured logs; handle logging where the error originates or at the call site.

Testing Updates

• Removed tests that asserted wrapper-level structured error logs for database constraints and Sequelize validation errors in both action and allAction test suites (eb08305). These tests no longer apply because the wrappers no longer enrich or re-log errors.

Release

• Promote from prerelease to stable: version updated to 4.4.83 (74cf8e7). This publishes the simplified error-handling behavior without additional API changes.

What to watch for / Migration

• Logging behavior change: You will see fewer logs from the wrappers themselves. If you depended on the wrapper to log error details (including constraint/detail or Sequelize validation arrays), add logging in your action/allAction implementations or at the call site to preserve that visibility.
• No API surface changes: The methods and their inputs/outputs are unchanged; only the wrapper-level logging and error-enrichment behavior was removed.