Requeueing a job without QueueAttribute forgets entered queue

When a job that doesn't have a QueueAttribute on its handler gets re queued, it is placed in the default queue instead of its originator queue.

I use the following code to add a job:

```
foreach (var client in clients)
{
BackgroundJobClient.Create(x => x.AddUser(user), new EnqueuedState(client.QueueId));
}
```

This is probably since it's a little bit sneaky to work around the specific queue problem, but I'd preferably not put attributes on every handler that I'd like to be routed (in my case I'd like everything to be routed to specific queues).

Possibly related to the solution of #228

The report uses BackgroundJobClient.Create with EnqueuedState and a handler without QueueAttribute; start there and trace how a requeued job selects its queue. Reproduce the default-queue behavior and verify that requeueing preserves the originating queue.

Written by the indexing model from the issue text.