chore(patches): add patches from upstream openresty

[catbro666]

Summary

Fixing the issue where a connection can't be setkeepalive successfully when using TLSv1.3. The issue was originally found in the tcp-log plugin.

ngx_lua patches

• openresty/lua-nginx-module@bf4bdcd
• openresty/lua-nginx-module@ea09d92
• openresty/lua-nginx-module@816483d

ngx_stream_lua patches

• openresty/stream-lua-nginx-module@5954e22
• openresty/stream-lua-nginx-module@69f0cd7
• openresty/stream-lua-nginx-module@1e1d93e

Checklist

• The Pull Request has tests
• A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
• There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Issue reference

https://konghq.atlassian.net/browse/FTI-6190

[bungle]

Doesn't apply cleanly, please fix these:

patching file bundle/ngx_lua-0.10.26/src/ngx_http_lua_socket_tcp.c
Hunk #1 succeeded at 5731 (offset 6 lines).
Hunk #2 succeeded at 5752 (offset 6 lines).

patching file bundle/ngx_stream_lua-0.0.14/src/ngx_stream_lua_socket_tcp.c
Hunk #1 succeeded at 5595 (offset 7 lines).
Hunk #2 succeeded at 5617 (offset 7 lines).

[bungle]

Also what is difference here compared to:
#13219 (which was not given approval to merge)

Aka is this fixing some real issue we want to fix. The LuaJIT was a real issue, but hard to reproduce. Just wanting to know how to react on these. Are we always good to merge them or is there some other logic and why the LuaJIT patch was not part of that logic.