introduce WARNING_OUT, when goto is not a hard error during tests

[gojimmypi]

Description

This is a revision of #6923 using a different source branch name as suggested.

Sometimes it may be desired to capture the call stack during test error conditions rather than just error out.

This PR introduces WARNING_OUT that will normally do the same thing as ERROR_OUT, except when an alterative is defined, such as the WOLFSSL_ESPIDF_ERROR_PAUSE for a custom ERROR_OUT handler in the Espressif environment.

Not all uses of the current ERROR_OUT are actually hard errors. Some simply capture expected but undesired results and still handle with the same ret = (err); goto eLabel; logic. The WARNING_OUT is used for situations where we don't actually want to capture a custom call stack with alternate ERROR_OUT code.

Note the ecc_test_curve_size test is one example now using WARNING_OUT instead of ERROR_OUT.

Other custom error-pausing code can easily be added as desired for other environments.

Also included is a variable-initialization for args in wolfcrypt_test_main().

Fixes zd# n/a

Testing

How did you test?

manual testing in Espressif environment.

Confirmation with:

./configure --enable-all && make clean && make && make check

Checklist

• added tests
• updated/added doxygen
• updated appropriate READMEs
• Updated manual and documentation

[JacobBarthelmeh]

Is this only used when WOLFSSL_ESPIDF_ERROR_PAUSE is defined? If so please move it down into that macro guarded section of code to avoid unused warnings.

[gojimmypi]

No, it wasn't the only place, but I cleaned up the other one that was hard-coded with "wolfcrypt_test" text.

There will be a separate, future exercise to replace references to printf with the Espressif ESP_LOG.

[JacobBarthelmeh]

@gojimmypi Sounds good, when replacing the printf's I recommend following the existing XPRINTF override pattern we have for using a custom printf in the tests.