Optimize "DisplayProcessTxDetails": Early exit if log level is not TRACE

[andreibancioiu]

Reasoning behind the pull request

• The function DisplayProcessTxDetails is called in a few places during transactions processing. Its main concern is to display some data by means of Log.Trace(). In this regard, it performs some computation, which takes some non-negligible time (analyzed with pprof).

Proposed changes

• Skip the computations performed by DisplayProcessTxDetails if it should display nothing, given the current log level.

Testing procedure

• Standard testing.

Pre-requisites

Based on the Contributing Guidelines the PR author and the reviewers must check the following requirements are met:

• was the PR targeted to the correct branch?
• if this is a larger feature that probably needs more than one PR, is there a feat branch created?
• if this is a feat branch merging, do all satellite projects have a proper tag inside go.mod?

[danidrasovean]

Normal allin test: v1.7.13-dev-config-aebb55e8e0 -> optimize-display-process-t-3b72d1056a

--- Specific errors ---

block hash does not match 1922
wrong nonce in block 860
miniblocks does not match 0
num miniblocks does not match 0
miniblock hash does not match 0
block bodies does not match 0
receipts hash missmatch 0

/------/

--- Statistics ---

Nr. of all ERRORS: 1
Nr. of all WARNS: 890
Nr. of new ERRORS: 1
Nr. of new WARNS: 10
Nr. of PANICS: 0

/------/