RFR: 7903383: jcstress: All State objects should be processed [v3]

[Aleksey Shipilev]

> There is a reasonable expectation that once `@State` object is created, it would eventually be acted upon. In fact, the Javadoc for `@Actor`/`@Arbiter` mentions that actor methods would be called on each state object exactly once. There are cases where users rely on this implicit lifecycle assumption to perform cleanups at `@Arbiter` methods.
> 
> Unfortunately, once jcstress leaves the test, it keeps last created state object slice unprocessed, which breaks this assumption.

Aleksey Shipilev 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 three additional commits since the last revision:

 - Merge branch 'master' into 7903383-state-lifecycle
 - Merge branch 'master' into 7903383-state-lifecycle
 - Fix

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

Changes:
  - all: https://git.openjdk.org/jcstress/pull/124/files
  - new: https://git.openjdk.org/jcstress/pull/124/files/cf169026..bc37cfec

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jcstress&pr=124&range=02
 - incr: https://webrevs.openjdk.org/?repo=jcstress&pr=124&range=01-02

  Stats: 18 lines in 1 file changed: 0 ins; 12 del; 6 mod
  Patch: https://git.openjdk.org/jcstress/pull/124.diff
  Fetch: git fetch https://git.openjdk.org/jcstress pull/124/head:pull/124

PR: https://git.openjdk.org/jcstress/pull/124