Fix for double ActiveJob::DeserializationErorr

[cristianbica]

If an argument that cannot be serialized is not in the first level of arguments (it's in an array or hash) the error is double wrapped inside DeserializationError. Example:

# enqueueing the Person object from the AJ testing wrapped in an array
RescueJob.enqueue [Person.new(404)]
# will raise 

> puts e.inspect
#<ActiveJob::DeserializationError: Error while trying to deserialize arguments: Error while trying to deserialize arguments: Cannot find person with ID=404>

> puts e.class.name
ActiveJob::DeserializationError

> puts e.original_exception.class.name
ActiveJob::DeserializationError

> puts e.original_exception.original_exception.class.name
Person::RecordNotFound

[matthewd]

I think we'd be better off moving the rescue to the outer/public deserialize method, and only using that once (i.e., not calling back to it in the Array case). It seems quite a waste of effort to potentially construct a stack of rescues that we'll end up ignoring.

[cristianbica]

@matthewd It's the same thing as serialize_argument will call serialize when it finds an array. So a traceback will look like this:
serialize -> calls serialize_argument and will rescue and wrap the exception
serialize_argument - will find an array or hash and call serialize
serialize -> calls serialize_argument and will rescue and wrap the exception
serialize_argument - will call GlobalID::Locator which will raise
So the exception raised by GlobalID::Locator will be rescued twice.