Bumping to Houdini Version: 13.0.449
Houdini Engine Version: 1.7 (API: 19)
Split results into call results and cook results. Finished support for exposing node errors, warnings, and messages.

- HAPI_GetCookingTotalCount(), HAPI_GetCookingCurrentCount(), HAPI_GetStatus(), HAPI_GetStatusStringBufLength(), and HAPI_GetStatusString() will no longer clobber the last call results.
- HAPI_STATUS_RESULT has now split into HAPI_STATUS_CALL_RESULT and HAPI_STATUS_COOK_RESULT.
- HAPI_STATUS_CALL_RESULT deals only with actual call to the API while HAPI_STATUS_COOK_RESULT deals with cook results (which normally run in a different thread). For example, calling HAPI_CookAsset() will generate a HAPI_STATUS_CALL_RESULT with the success/failure of the call itself to HAPI_CookAsset() while eventually filling a HAPI_STATUS_COOK_RESULT with the results of the actual cook.
- HAPI_STATUS_STATE has been renamed to HAPI_STATUS_COOK_RESULT for consistency.
- Nodes will be parsed to retrieve node errors, warnings and messages ONLY during the call to HAPI_GetStatusStringBufLength() and ONLY for the previously cooked asset(s). The (s) is for when loading a whole Houdini scene and cooking all assets in it. This is also why HAPI_GetStatusStringBufLength() is the one that takes in the HAPI_StatusVerbosity setting. It's up to you to decide when to call for cook results and with what verbosity. The general rule of thumb is to call it when the cook has failed (HAPI_STATE_READY_WITH_COOK_ERRORS is returned as the READY cook state) or no/invalid geometry has been retrieved.