Split up C API smoke test into more dynamic sections (#5456)

As discussed in a recent debugging call, the C API "smoke test" failed
non-deterministically with a SEGV in a recent CI run. We are adding more
dynamic sections to the test in order to get more info about where the
SEGV occurred, since we do not yet have a stack trace.

This pull request splits things up into one dynamic section per read
query.

Output of `./tiledb_unit -d yes --vfs=native "C API: Test a dynamic
range of arrays"` looks something like
```
...
1.475 s: sparse array with 3 attribute(s) and 3 dimension(s).col-major cells, col-major tiles, unordered writes, AES_256_GCM encryption
1.492 s: C API: Test a dynamic range of arrays
0.000 s: unordered reads, [6] conditions, OR
1.512 s: sparse array with 3 attribute(s) and 3 dimension(s).col-major cells, col-major tiles, unordered writes, AES_256_GCM encryption
1.530 s: C API: Test a dynamic range of arrays
0.000 s: unordered reads, [7] conditions, AND
1.488 s: sparse array with 3 attribute(s) and 3 dimension(s).col-major cells, col-major tiles, unordered writes, AES_256_GCM encryption
1.502 s: C API: Test a dynamic range of arrays
0.000 s: unordered reads, [7] conditions, OR
...
```

---
TYPE: IMPROVEMENT
DESC: split C API smoke tests up into one dynamic section per read query

Author: rroelke