ssl_stream doesn't use BOOST_BEAST_ASYNC_TPARAM1 due to clang errors.

[klemens-morgenstern]

Closes #2661

[cppalliance-bot]

Timeline tracing charts: https://2683.beast.tracing.cppalliance.org/index.html

[codecov]

Codecov Report

Merging #2683 (ff041a1) into develop (e65aff4) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #2683   +/-   ##
========================================
  Coverage    92.97%   92.97%           
========================================
  Files          177      177           
  Lines        13658    13658           
========================================
  Hits         12698    12698           
  Misses         960      960           

Impacted Files	Coverage Δ
include/boost/beast/ssl/ssl_stream.hpp	0.00% <ø> (ø)

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e65aff4...ff041a1. Read the comment docs.

[klemens-morgenstern]

@vinniefalco this is technically a derivation from asio best practices for a compiler bug. I could use some input from you.

[sfjhkjdsh]

maybe you can have a compiler switch just for clang

#ifdef __clang__
template<class AsyncStream, typename TeardownHandler>
#else
template<class AsyncStream, BOOST_BEAST_ASYNC_TPARAM1 TeardownHandler>
#endif

[klemens-morgenstern]

I'll merge this, because the async_teardown isn't usually called directly but by websocket::stream::async_close.

So not having the concept check should be fine.