Some job state rows for Processing have earlier CreatedAt than rows for Enqueued

We are seeing that on some jobs, the Processing state shows as occurring before the Enqueued state. The dashboard shows a negative time difference between the two states, and querying the rows in the Hangfire.State table, the Processing state row is in fact earlier than the Enqueued state row.

We are running two web servers against a single Hangfire database, so it seems like a time difference between the two servers could account for the issue. Hangfire.SqlServer appears to use the ASP.NET time rather than the database's time. One piece I can't explain though is that sometimes we're seeing this with jobs processed by web server #1 and other times it's web server #2.

See the negative time difference for Processing:

Hangfire.Core and Hangfire.SqlServer version 1.6.17

The recurring job has the following attributes:
```
[DisableConcurrentExecution(30)]
[AutomaticRetry(Attempts = 0, OnAttemptsExceeded = AttemptsExceededAction.Delete)]
```

The source code for adding the job:
`RecurringJob.AddOrUpdate(JobName, svc => svc.FetchNewImportJobsAsync(CancellationToken.None), "*/1 * * * *", queue: "recurring");`

The recurring queue is setup as follows:
```
var serverOptions = new BackgroundJobServerOptions
{
Queues = new [] { "recurring" },
WorkerCount = 1
};

app.UseHangfireServer(serverOptions);
```

Start with the Hangfire.SqlServer behavior that records CreatedAt values in the Hangfire.State table, using the reported two-server setup as the reproduction context. Compare the timestamps produced by the recurring job entry point, RecurringJob.AddOrUpdate, and the server setup using app.UseHangfireServer; done means Processing no longer precedes Enqueued and the dashboard shows a non-negative difference.

Written by the indexing model from the issue text.