bug#38072: when `byte-compile-file' finds out that a file is `no-byte-compile', it ignores `load' parameter

[Paul Pogonyshev]

After (byte-compile-file "..." t) one normally expects that the file
is loaded, all its functions and variables are visible etc.  However,
if file contains local variable `no-byte-compile', not only
compilation is cancelled, `byte-compile-file' also doesn't load the
file.

Expected: if `byte-compile-file' cancels byte-compilation and `load'
is non-nil, it should load the uncompiled source instead.

Paul