streams: tidy the wrapper error log on every open_wrapper return

[iliaal]

Until d75f79e the tidy call sat on the single return path of _php_stream_open_wrapper_ex(), so it ran whether or not the opener produced a stream. The early-return refactor duplicated it into the three failure branches, and 605ff6e then folded those into a shared cleanup: while keeping only the copy in the opener-failure branch. Openers run with REPORT_ERRORS masked and store into FG(wrapper_logged_errors) instead of printing, so anything stored by an opener that goes on to succeed now survives until request shutdown and is replayed by the next failure for the same wrapper.

I could not build a userland reproducer: every built-in opener that stores a message returns NULL right after, and instrumenting the shared cleanup produced no hit across the test suite. The invariant is still that the list only holds messages for an open that is in flight, so this restores it rather than fixing an observable symptom.

[Girgias]

I don't really see why it needs to be at the end? But if you want it to be called regardless I would prefer for it to added after the UNEXPECTED(!stream) branch as no other messages will be added to the log.

[iliaal]

It doesn't, cleanup: was just the one point every post-opener return passes through. Added after the branch instead.