RFR: 8263476: Use reserved memory for stack guard pages [v4]

[Albert Mingkun Yang]

> Use reserved (instead of committed) memory for stack-guard-pages on linux like systems.
> 
> `os::must_commit_stack_guard_pages` uses `commit` in its name, but `commit` usually has specific meanings in OS memory context. The actual question the caller is asking is whether the caller needs to do some preparation work before marking the guard-pages as inaccessible. To avoid confusion, I changed it to "allocate". Other suggestions are welcome.
> 
> Test: ~tier1-3~ tier1-8

Albert Mingkun Yang has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes brought in by the merge/rebase. The pull request contains five additional commits since the last revision:

 - Merge branch 'master' into no-commit-stack-guard-page
 - review
 - review
 - Merge branch 'master' into no-commit-stack-guard-page
 - no-commit-stack-guard-page

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

Changes:
  - all: https://git.openjdk.org/jdk/pull/26571/files
  - new: https://git.openjdk.org/jdk/pull/26571/files/a248cff8..db7647fb

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jdk&pr=26571&range=03
 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=26571&range=02-03

  Stats: 9769 lines in 303 files changed: 6276 ins; 2452 del; 1041 mod
  Patch: https://git.openjdk.org/jdk/pull/26571.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/26571/head:pull/26571

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