RFR: 8361844: Build without C1 or C2 fails after 8360707

[Andrew Dinn]

After [JDK-8360707](https://bugs.openjdk.org/browse/JDK-8360707) builds which omit C1 or C2 can generate an exploded jdk which fails on startup with an assert:

    assert(idx2 >= 0 && idx2 >= idx1) failed: bad blob ids first -1 and second -1

The problem is that the blob and stub id verification expects the blob, stub and entry ranges in the C1 and C2 stub groups to be positive. However, when C1 or C2 is omitted the associated range starts and ends are NO_BLOBID, NO_STUBID and NO_ENTRYID (all -1) and this breaks some of the internal consistency checks that test the span of blob, stub and entry ranges.

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

Commit messages:
 - fix issue after 8360707 when C1 or C2 omitted

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

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