`rawdb` methods never return errors

[alarso16]

I spoke in the office with @StephenButtolph about how unreliable these rawdb methods are, where any write can log.Crit and any read returns no error, which is terrible handling. To avoid all these zero values floating around and undiagnosable database errors, it may be better to consider finding a libevm solution to this, by returning errors when one occurs and some lint job . This may be very invasive though...

Originally posted by @alarso16 in #5555 (comment)