Add %0 format to run-tests.php

[nikic]

This format matches against null bytes, and prevents the test
expectation from being interpreted as binary data.

bless_tests.php will automatically replace \0 with %0 as well.

[nikic]

If you're wondering what's going on here, it appears to be a bug in GitHub's diff viewer. The 00efgh\xijkl suffix on these lines is present in the old version as well, but GitHub doesn't display it in the side-by-side diff view.

[TysonAndre]

This will cause issues with urlencode for values such as %00 and %0a(\n) and %09(\t) https://github.com/igbinary/igbinary/blob/3.2.2/tests/igbinary_088.phpt (the run-tests diff has the same string in both)

• Users who didn't see that thread would have a harder time figuring out why

Or for printf format strings such as printf("%012d", 1); when the format strings themselves are printed

But this is an obscure use case, and %d and %f already had this problem - it was just less often due to most binary data being ascii.

I wonder if it'd make sense to add a note to the diff output section if the actual and expected lines were exactly the same in EXPECTF sections to save time for users and answering questions about this

006+ %00%00%00%02%17%01X%14%03%11%05name0%00%11%05name1%00%11%05name2%00
006- %00%00%00%02%17%01X%14%03%11%05name0%00%11%05name1%00%11%05name2%00

006- %00%00%00%02%17%01X%14%03%11%05name0%00%11%05name1%00%11%05name2%00 (%0 means the null byte in EXPECTF in run-tests.php of php 8.1+)

(or a different symbol such as 006? (%0 means the null byte in run-tests.php of php 8.1+) for the new explanation

(and similar messages for %s, %S, %d, etc.)

---

I'm already switching to str_replace(['\\', '%'], ['\\\\', '\x'], urlencode($ser)) and only two test files used the combination of EXPECTF and urlencode on binary data