Fix use-after-move in //components/services/storage/indexed_db/scopes/

Fix use-after-move (potential) bugs found by the
"bugprone-use-after-move" clang-tidy check.

Bug: 1122844
Change-Id: I2a2c320dd225f41f998e834aa3781f5a46e0a0d9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2382319Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Commit-Queue: Maksim Ivanov <emaxx@chromium.org>
Cr-Commit-Position: refs/heads/master@{#803570}

components/services/storage/indexed_db/scopes/disjoint_range_lock_manager.cc

@@ -193,7 +193,7 @@ void DisjointRangeLockManager::LockReleased(int level, ScopeLockRange range) {
       auto released_callback = base::BindOnce(
           &DisjointRangeLockManager::LockReleased, weak_factory_.GetWeakPtr());
       // Grant the lock.
-      requester.locks_holder->locks.emplace_back(std::move(range), level,
+      requester.locks_holder->locks.emplace_back(range, level,
                                                  std::move(released_callback));
       std::move(requester.acquired_callback).Run();
       // This can only happen if acquired_count was 0.