concurrency: use of lock.Modes to determine confilcts in tryActiveWait

This patch refactors tryActiveWait to make use of lock.Modes to
determine conflicts. In doing so, it splits out the logic into 3
different methods:

1. To determine a conflict with a lock holder.
2. To determine a conflict with a reservation.
3. To modify datastructures in preparation for active wait.

In doing so, we no longer make the assumption that there will only
ever be a single reservation or lock holder on a key. In the future,
we'll be able to further extend tryActiveWait to account for multiple
locks/reservations on a key.

Informs #102210

Release note: None

pkg/kv/kvserver/concurrency/BUILD.bazel

@@ -18,6 +18,7 @@ go_library(
     deps = [
         "//pkg/kv",
         "//pkg/kv/kvpb",
+        "//pkg/kv/kvserver/concurrency/isolation",
         "//pkg/kv/kvserver/concurrency/lock",
         "//pkg/kv/kvserver/concurrency/poison",
         "//pkg/kv/kvserver/intentresolver",