kick does not abort render or display ERROR log messages when usd file has arnold:global:log:verbosity

**Describe the bug**
If a usd file has **arnold:global:log:verbosity**, like this (verbosity level doesn't matter):

```
def RenderSettings "rendersettings"
{
custom int arnold:global:log:verbosity = 5
}
```
Then when you kick a usd file that has something wrong with it (like a missing texture), all you get is this:

```
| starting 32 bucket workers of size 64x64 ...
WARNING | render terminating early: received abort signal
| render done in 0:00.006
| [driver_exr] writing file `C:/Users/blairs/untitled.arnold_rendersettings1.0049.exr'
00:00:02 279MB WARNING | [kick] render aborted due to earlier errors
| render done
```

Note that the error aborts, but there are no ERRORs logged. And an output file is written to disk.

If you remove **arnold:global:log:verbosity**, then you get the ERROR messages. But the output file is still written to disk.

```
00:00:02 267MB | starting 32 bucket workers of size 64x64 ...
00:00:02 288MB ERROR | [texturesys] /materials/arnold_utility/image1: ImageInput::create() called with no filename
Invalid image file "": ImageInput::create() called with no filename
00:00:02 294MB ERROR | [texturesys] /materials/arnold_utility/image1: Invalid image file "": ImageInput::create() called with no filename
00:00:02 294MB ERROR | [texturesys] /materials/arnold_utility/image1: Invalid image file "": ImageInput::create() called with no filename
00:00:02 294MB WARNING | [kick] render aborted due to earlier errors
00:00:02 294MB ERROR | [texturesys] /materials/arnold_utility/image1: Invalid image file "": ImageInput::create() called with no filename
00:00:02 294MB ERROR | [texturesys] /materials/arnold_utility/image1: Invalid image file "": ImageInput::create() called with no filename
00:00:02 295MB WARNING | render terminating early: unknown reason
00:00:02 295MB | render done in 0:00.040
00:00:02 295MB | [driver_exr] writing file `C:/Users/blairs/untitled.arnold_rendersettings1.0049.exr'
```

**To Reproduce**
Steps to reproduce the behavior:
1. kick this usd file: [missing.zip](https://github.com/Autodesk/arnold-usd/files/14485204/missing.zip)
For example: `kick -v 5 -dp -dw missing.usda`

**Expected behavior**
The render aborts, ERRORs are printed, and nothing is written to disl.

**Used Software Versions**
- Arnold: 7.2.5.2

Start by running `kick -v 5 -dp -dw missing.usda` from the `missing.zip` reproduction and compare it with the same file without `arnold:global:log:verbosity`. Trace the kick/render path implicated by the logging and output-file behavior; done means ERROR messages are preserved, the render aborts, and no output file is written.

Written by the indexing model from the issue text.