RFR: 8322954: Shenandoah: Convert evac-update closures asserts to rich asserts

[Aleksey Shipilev]

Over the years, we seem to have introduced new asserts that should really be the rich Shenandoah asserts. I looked around and found at least three places in evac-update closures.

We also do not need ` _mark_context->is_marked(resolved)` in `ShenandoahEvacUpdateCleanupOopStorageRootsClosure`, because evac-ed objects are supposed to be after TAMS and thus implicitly marked.

Additional testing:
 - [x] macos-aarch64-server-fastdebug, `hotspot_gc_shenandoah`
 - [ ] linux-x86_64-server-fastdebug, `tier{1,2,3}` with `-XX:+UseShenandoahGC`

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

Commit messages:
 - Work

Changes: https://git.openjdk.org/jdk/pull/17245/files
 Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=17245&range=00
  Issue: https://bugs.openjdk.org/browse/JDK-8322954
  Stats: 6 lines in 3 files changed: 1 ins; 3 del; 2 mod
  Patch: https://git.openjdk.org/jdk/pull/17245.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/17245/head:pull/17245

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