Parser: return error if stream encountered when allowStreams = false

Opening a PDF file where the first object is a stream prints a
"Command token too long" error message. This is caused by the
Linearization check in Linearization::Linearization reading objects
with allowStreams = false. The Parser ignores the "stream" token and
tries reading the next token which is usually binary data. Setting
allowStreams to true will not work since the stream length is often an
indirect object and at this point the XRef has not been created.

Fix this by making Parser return an error object if the "stream" token
is encountered when allowStreams is false.

Bug 58966
Initialize refLine totally

Fixes uninitialized memory read in 1004.pdf.asan.7.3
Do not crash in broken documents like 1007.pdf.asan.48.4
Forgot the C of the last commit
Fix crash in broken file 1031.pdf.asan.48.15
Fix invalid memory accesses in 1036.pdf.asan.23.17
Fix invalid memory accesses in 1091.pdf.asan.72.42
Fix another invalid memory access in 1091.pdf.asan.72.42
Fix invalid memory access in 2030.pdf.asan.69.463
Fix invalid memory access in 1150.pdf.asan.8.69
Use CPPFLAGS for CPPFLAGS not CFLAGS

Bug #59186
Add a null check for gfxFont

Bug #59561
Update C
Update C year here too
0.22.1