Added Renesas RX TSIP AES CTR support

[dgarske]

Description

Changes to support Renesas RX TSIP AES CTR. Fix to increment IV for AES CTR with TSIP (allow encrypt to be called multiple times without having to manually reset the IV). Add build guards on the crypto callback ECC items. Fixed issues with ecc_onlycb_test.

Testing

Checklist

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

[dgarske]

Retest this please. Agent offline exception.

[dgarske]

Jenkins retest this please "history lost"

[dgarske]

Jenkins Retest this please. "fsanitize aborted"

[dgarske]

@miyazakh will you please review these TSIP changes to support AES CTR?

[dgarske]

Retest this please: "Found unhandled hudson.remoting.RequestAbortedException exception:"

[dgarske]

Jenkins retest this please

History already deleted, but same flakey tests:

• Build wolfSSL » PRB-140-3-tests completed: FAILURE
• Build PRB-fipsv2-regression-and-rolling-release-v3 completed: FAILURE
• Build PRB-generic-config-parser completed: FAILURE

[dgarske]

@miyazakh I am okay with the unit-test calling the tsip_AesCtr API directly. It could set the crypto callback and use the wc_AesCtrEncrypt API. You are welcome to push updates directly to my branch.

[dgarske]

Retest this please:

PRB-fsanitize-addr-v3

./configure --enable-jobserver=4 CC="clang -fsanitize=address,undefined -g" --enable-all --enable-smallstack
FAIL: scripts/ocsp-stapling_tls13multi.test

PRB-single-flag.txt_125: RB-long-runtime.txt_1: PRB-disable-options.txt_9:

+ cat test-suite.log
cat: test-suite.log: No such file or directory
script returned exit code 1

PRB-dtls.txt_27: PRB-known-configs.txt_80: Found unhandled org.jenkinsci.plugins.workflow.support.steps.AgentOfflineException exception: