RFR: 8226416: MonitorUsedDeflationThreshold can cause repeated async deflation requests

[Daniel D.Daugherty]

Adding support for a diagnostic option called NoAsyncDeflationProgressMax
with a default value of 3. If we have three async monitor deflation cycles in a
row with zero monitors deflated, then we adjust the in_use_list_ceiling up.

I've locally built and tested this fix on my MBP13 using the
MonitorUsedDeflationThresholdTest.java test that I wrote when this issue
first came up in June of 2019. I will be including this fix in my next Mach5
Tier[1-3] testing batch.

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

Commit messages:
 - 8226416: MonitorUsedDeflationThreshold can cause repeated async deflation requests
 - 8259349: -XX:AvgMonitorsPerThreadEstimate=1 does not work right
 - 8259397: ThreadsSMRSupport::print_info_on() should use try_lock_without_rank_check()

Changes: https://git.openjdk.java.net/jdk/pull/1993/files
 Webrev: https://webrevs.openjdk.java.net/?repo=jdk&pr=1993&range=00
  Issue: https://bugs.openjdk.java.net/browse/JDK-8226416
  Stats: 40 lines in 4 files changed: 34 ins; 0 del; 6 mod
  Patch: https://git.openjdk.java.net/jdk/pull/1993.diff
  Fetch: git fetch https://git.openjdk.java.net/jdk pull/1993/head:pull/1993

PR: https://git.openjdk.java.net/jdk/pull/1993