Fix Ruby 3.2+ compatibility in aws-sdk-neptunedata detailed_message overrides

[ricardogpsf]

Summary

In Ruby 3.2, Exception#full_message was updated to internally call detailed_message(highlight:) passing a keyword argument (source). All 34 error classes in aws-sdk-neptunedata override detailed_message to expose the API-level detailed_message field, but none accepted the highlight: keyword — causing an ArgumentError whenever Ruby or tooling calls full_message on these exceptions.

A common trigger is OpenTelemetry SDK's span.record_exception(e), which calls e.full_message(highlight: false, order: :top) to capture the stacktrace. This silently breaks tracing and any instrumentation that records Neptune exceptions on spans.

Change

Added highlight: true, ** to all 34 detailed_message overrides in errors.rb and updated the corresponding .rbs type signatures.

# Before
def detailed_message
  @data[:detailed_message]
end

# After
def detailed_message(highlight: true, **)
  @data[:detailed_message]
end

Backward Compatibility

Fully backward compatible. Keyword arguments with defaults are valid Ruby syntax since 2.0. In Ruby < 3.2, full_message never calls detailed_message with keyword arguments, so the added parameter is never passed — no behavior change.

Note on Code Generation

errors.rb and sig/errors.rbs are generated files. The corresponding generator template will also need to be updated to preserve this fix on future regeneration.