chore: local -> external builder mapping

[namn-grg]

Overview

This PR adds payload ID mapping functionality to track and map between local and external payload IDs when interacting with the builder node. This ensures proper correlation between payloads across different nodes.

Key changes:

• Added local_to_external_payload_ids cache to PayloadTraceContext to store mappings
• Added methods to store and retrieve payload ID mappings
• Updated get_payload_v3 to use external payload ID when requesting from builder
• Added payload ID mapping in fork_choice_updated_v3 response handling
• Added logging improvements to track both local and external payload IDs

The changes help maintain proper tracing and correlation between local execution engine payloads and external builder payloads, improving debuggability and reliability of the system.

fixes #46

[namn-grg]

@avalonche can you pls check if the logic makes sense?
Its currently failing failing test

'server::tests::test_server' panicked at src/server.rs:760:9:
assertion `left == right` failed
  left: 0
 right: 1

[dmarzzz]

thanks for the PR! will review soon!

[avalonche]

LGTM, it'll be great if you can add some tests asserting when

1. payload ids are the same
2. payload ids are different
   and check that the correct payload id is used.
   Also there seems to be lint issues

[namn-grg]

Thanks for the review @avalonche . Addressed it!

[avalonche]

I've fixed some failing tests here

[namn-grg]

Thanks! I see it was about running the tests sequentially. Personally not a fan of having all of them under test_server just looks dirty. Can be considered to use serial_test for it.