bug#31556: 27.0.50; Reading a certain invalid bytecode object triggers an assertion

[Pip Cet]

This looks like a potential security issue in builds without debugging
assertions, as essentially random memory is written to in the ASET. I
don't know precisely when load-force-doc-strings is non-nil, but I
suspect it's rare. (It's probably also possible to construct a file
which, when loaded, will segfault because it contains a docstring that
doesn't end in \037, but that's not a real issue as loading a corrupt
file will result in potentially dangerous operations anyway.)