Follow-up: Remove legacy_wal_location from SidekiqServerMiddleware

In #325291 (closed) we introduced legacy_wal_location because already scheduled jobs could still contain the legacy database write location in job hash. Once !66280 (closed) is deployed on production, we can remove this legacy code as part of next iteration