[11.x] Refine error messages for detecting lost connections (Debian bookworm compatibility)

[mfn]

Summary

Same as #53794 , which was for L10, but this time for L11 (I thought there was some kind of L10 -> L11 merge, but alas, there isn't)

Paraphrasing from the other PR:

Last year I added those two via #47398 Please see details and reasoning there, it still applies; TL;DR:

Ever since I moved from AWS Aurora to using AWS RDS Proxy, which
(similar to pgbouncer) is essential to not overload the primary database
with connection, I sporadically see these messages. This affects
scheduled tasks, worker, HTTP requests; it's across the whole board.

What I didn't knew back then was that the order/format of those messages very much dependent on the underlying libraries (libpq and or libssl presumably) and once we started to upgrade from Debian bullseye to bookworm, they changed and now are randomly interrupting our service again.

The new (complete) messages look like this:

SQLSTATE[08006] [7] connection to server at "…" (…), port 5… failed: SSL error: sslv3 alert unexpected message (Connection: main, SQL: …

That is, it still contains "SSL error: sslv3 alert unexpected message" but there's now connection specific information after the SQLSTATE prefix.

Since lost connection detection is based on exact string matching and not regex, we're just removing the magic numbers in front and still keep backwards compatibility.

Notes

Please accept this this PR against Laravel 10.x because we're still using and it requires the fix there (we're in the progress moving to L11, but it still takes time).

Thanks!