docs(evm): correct the blockTag field comment to list all three accepted tags

FinalityConfig.BlockTag's own comment said state is read at finalized
or safe, but Validate has accepted latest as a third legal value since
it was introduced for the local, instant-mining test harness. The
comment now names all three and repeats, next to the field itself,
what BlockTagLatest's own doc comment already says: it carries no
reorg protection and is only appropriate for a local chain.

No behavior changes; latest was already accepted before this commit.

Signed-off-by: atharrva01 <atharvaborade568@gmail.com>

Author: atharrva01

x/token/services/network/evm/config.go

@@ -80,7 +80,8 @@ type ContractsConfig struct {
 
 // FinalityConfig controls how transaction finality is observed.
 type FinalityConfig struct {
-	// BlockTag is the tag state is read at (finalized or safe).
+	// BlockTag is the tag state is read at: finalized (default, no reorg risk), safe, or latest (no
+	// reorg protection at all; only appropriate for a local, instant-mining chain).
 	BlockTag string `yaml:"blockTag"`
 	// PollInterval is the delay between status polls.
 	PollInterval time.Duration `yaml:"pollInterval"`