RFR: 8313202: MutexLocker should disallow null Mutexes

[Aleksey Shipilev]

As seen in [JDK-8313081](https://bugs.openjdk.org/browse/JDK-8313081), it is fairly easy to pass nullptr `Mutex` to `MutexLocker` by accident, which would just silently avoid the lock.

There are a few places in Hotspot where we pass `nullptr` to simulate re-entrancy and/or conditionally take the lock. Those places can be more explicit, and the default `MutexLocker` can disallow nullptrs for extra safety.

Open for some bikeshedding on the names of the new `MutexLockers`. Particularly `ReentrantMutexLocker` might lull readers into believing it does safepoint checks on re-entrant "lock", which it actually does not do.

More thorough testing with different GC/JIT combinations is running now, we might find more issues there. Meanwhile, please comment on the approach.

Additional testing:
 - [x] `grep -R "MutexLocker " src/hotspot | grep -i null`, no hits
 - [x] `grep -R "MutexLocker " src/hotspot | grep -i ?`, no hits
 - [x] Linux AArch64 fastdebug, `tier1 tier2 tier3` (re-run in progress)

-------------

Commit messages:
 - Workaround for JDK-8313210
 - Fixing CodeCache analytics
 - Initial work

Changes: https://git.openjdk.org/jdk/pull/15043/files
 Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=15043&range=00
  Issue: https://bugs.openjdk.org/browse/JDK-8313202
  Stats: 104 lines in 15 files changed: 44 ins; 13 del; 47 mod
  Patch: https://git.openjdk.org/jdk/pull/15043.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/15043/head:pull/15043

PR: https://git.openjdk.org/jdk/pull/15043