Fix connection error when the reason is empty

[Sebastix]

It seems not every websocket server is responding with a reason, for example wss://nostr.wine
I found it while I was debugging some WebSocket connections, see nostrver-se/nostr-php#82 (comment) and I also reached out to the server operator: https://njump.me/nevent1qvzqqqqqqypzq0vy9tlv6h3f8u5tvcnexdcy50acec2n42ga0y9tz8m2w5k5ffpdqyv8wumn8ghj7enfd36x2u3wdehhxarj9emkjmn99uq3samnwvaz7tmrv4kxcctj9ehx7um5wgh8w6twv5hsqgrlme92sxxstf3dvha5a78mnrz9ea7eguaaw2lrvjxtu460y9fz0ykfrp9c

With this change the regex is less strict allowing an empty reason.

[coveralls]

Pull Request Test Coverage Report for Build 13249804768

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 12707033125:	0.0%
Covered Lines:	1057
Relevant Lines:	1057

---

💛 - Coveralls

[sirn-se]

Runs fine, thanks for contributing.
Will be included in next version.

[sirn-se]

Version 3.2.3 now released, including this PR.