Always reinitialize the SSL cipher suites in InitSSL_Side as the side and enabled algos have likely changed.

[kareem-wolfssl]

Description

Fixes #7735.

Testing

Using example client:

./configure --disable-dependency-tracking --enable-certgen --enable-des3 --enable-dh --enable-dsa --enable-dtls --enable-ecc --enable-fastmath --enable-fasthugemath --enable-keygen --enable-opensslall --enable-opensslextra --enable-ripemd --enable-secure-renegotiation --enable-sessioncerts --enable-session-ticket --enable-sp --enable-sp-asm --enable-sp-math-all --enable-sha512 --enable-shared --enable-sni --enable-ssh --enable-static --enable-tls13 --enable-debug 'CFLAGS=-DWOLFSSL_ALT_NAMES -DFP_MAX_BITS=8192 -DNO_WOLFSSL_STUB -DWOLFSSL_ALT_CERT_CHAINS -DHAVE_IO_TIMEOUT -DWOLFSSL_NO_ASN_STRICT -DWOLFSSL_LOGGINGENABLED_DEFAULT=1' --enable-debug --enable-debug-trace-errcodes
./examples/client/client -v d -h media.ccc.de -p 443 -d
./examples/client/client -v e -h media.ccc.de -p 443 -d

Before this change only the client_method command (first client command) was connecting due to a difference in enabled cipher suites.

Using curl built against the above configure line, replace the wolfSSL method (req_method) with wolfSSLv23_method or wolfSSLv23_client_method, then build and connect to fsf.org with: curl -v https://fsf.org. curl will not connect with wolfSSLv23_client_method before this change.

Checklist

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