fix: handle error[BNB-16]

[welkin22]

Description

1. In core/state_prefetcher.go:Prefetch() function, the error of the precacheTransaction() call is not handled.
2. The gopool/pool.go:Submit() function returns an error, but none of the callers handle it. Based on our analysis, since the
   defaultPool is not created with the Nonblocking flag, the underlying call defaultPool.Submit() does not expect an error. In this case, it is recommended to consider changing the function signature of pool.go:Submit() to not return an error and instead log an error message within the function.
3. In core/blockchain.go:writeBlockWithState()#L1440 , the error is not handled in the call of bc.triedb.Commit() .
4. In core/blockchain.go:writeBlockWithState()#L1421 function, the error is not handled in the call of bc.triedb.Cap().

Rationale

There are several places not handling returning error.

Example

none

Changes

Notable changes:

• log the error of the precacheTransaction() call
• pool.submit no longer returns an error, instead recording an error log
• The two places where errors are not handled will directly return errors. This will cause the logic that continued when an error was encountered in the past to be directly interrupted. Need to confirm whether there is a problem.