chore(observability): add tokio runtime with custom thread naming

[yongkangc]

Closes: #18624 - All threads looked identical - impossible to debug or profile

• better observability of tokio threads for profiling, similar to how we doing it on rayon i.e reth-rayon-36

Changes:

• All major thread pools now have descriptive names for easy identification:
  • Main CLI runtime: cli-tokio-{id} (e.g., reth-cli-tokio-0, reth-cli-tokio-1)
  • Workload executor: wkp-tokio-{id} (e.g., reth-wkpool-tokio-0, reth-wkpool-tokio-1)
  • Trie operations: trie-tokio-{id} (e.g., reth-trie-tokio-0, reth-trie-tokio-1)
  • CPU blocking tasks: blk-rayon-{id} (e.g., reth-blocking-rayon-0, reth-blocking-rayon-1)
  • Global CPU pool: reth-rayon-{id} (e.g., reth-rayon-0, reth-rayon-1)

[yongkangc]

reth-wkpool-tokio or reth-trie-tokio threads, because the runtime will already be initialized upstream

@shekhirin you were right!

ran it on samply and seems like trie-tokio, wkp-tokio doesnt get created because we use the main runtime.

however, think we should still keep the fallback name (trie-tokio, wkp-tokio) threads just in case it fallsbacks and we wanna know whats the run time - that would still be helpful at no cost

although - the blocking one would still be relevant

[shekhirin]

some naming suggestions

[yongkangc]

@shekhirin thanks for the suggestions, i think its much more intuitive now - let me know if u have any other comments!