using `coerce_with:` lambda without root `Exception` difficult to *debug* unless we help Grape `coerce_value`

in method Grape::Validations::CoerceValidator#coerce_value we loose the root cause of Exception leading to a Types::InvalidValue

Consequence is that the dry-validate errors is somewhat not very helpful

example
I got a params validator that read

coerce_with: ->(val) {
                   (val.nil? || val.empty?) ? nil : Types::PrimaryKey.(val) },

which was obvious to debug after changing

def coerce_value(val)
        converter.call(val)
      # Some custom types might fail, so it should be treated as an invalid value
      rescue StandardError
        Types::InvalidValue.new
      end

to

def coerce_value(val)
        converter.call(val)
      # Some custom types might fail, so it should be treated as an invalid value
      rescue StandardError => e
        Types::InvalidValue.new(e.message)
      end

as indeed Integer#empty? does not exists.

Do you think its reasonable to add this for calling Types::InvalidValue initialiser ?

Locate Grape::Validations::CoerceValidator#coerce_value and inspect how Types::InvalidValue is initialized. Reproduce the shown coerce_with lambda failure, then verify that the resulting validation error preserves the original exception message without changing successful coercion behavior.