UPSTREAM: locking/csd_lock: Remove per-CPU data indirection from CSD lock debugging

The diagnostics added by this commit were extremely useful in one instance:

a5aabace ("locking/csd_lock: Add more data to CSD lock debugging")

However, they have not seen much action since, and there have been some
concerns expressed that the complexity is not worth the benefit.

Therefore, manually revert the following commit preparatory commit:

de7b09ef ("locking/csd_lock: Prepare more CSD lock debugging")

Bug: 326196720
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Juergen Gross <jgross@suse.com>
Link: https://lore.kernel.org/r/20230321005516.50558-3-paulmck@kernel.org


(cherry picked from commit 6366d062)
Signed-off-by: Qais Yousef <qyousef@google.com>
Change-Id: I18a9ad9aa9f065c0aefc7c3457046109f676df86
(cherry picked from commit 8cfe78e6db8a7ad22bfcf63a1930e7b694e58542)
Signed-off-by: Qais Yousef <qyousef@google.com>