filtered out the noisy Invalid Trace log messages

[macfarla]

PR description

Added a filter for the"Invalid TraceId in B3 header" log

Fixed Issue(s)

Fixes #6440

Thanks for sending a pull request! Have you done the following?

• Checked out our contribution guidelines?
• Considered documentation and added the doc-change-required label to this PR if updates are required.
• Considered the changelog and included an update if required.
• For database changes (e.g. KeyValueSegmentIdentifier) considered compatibility and performed forwards and backwards compatibility tests

Locally, you can run these tests to catch failures early:

• unit tests: ./gradlew build
• acceptance tests: ./gradlew acceptanceTest
• integration tests: ./gradlew integrationTest
• reference tests: ./gradlew ethereum:referenceTests:referenceTests

[macfarla]

Node where I added this config after a short time - number stays same

sallymacfarlane@dev-elc-besu-teku-sepolia-dev-sally-control:~$ grep -c B3Prop /var/log/besu/besu.log
27
sallymacfarlane@dev-elc-besu-teku-sepolia-dev-sally-control:~$ grep -c B3Prop /var/log/besu/besu.log
27
sallymacfarlane@dev-elc-besu-teku-sepolia-dev-sally-control:~$ grep -c B3Prop /var/log/besu/besu.log
27
sallymacfarlane@dev-elc-besu-teku-sepolia-dev-sally-control:~$ grep -c B3Prop /var/log/besu/besu.log
27
sallymacfarlane@dev-elc-besu-teku-sepolia-dev-sally-control:~$ grep -c B3Prop /var/log/besu/besu.log
27
sallymacfarlane@dev-elc-besu-teku-sepolia-dev-sally-control:~$ grep -c B3Prop /var/log/besu/besu.log
27

Node without this config - number go up

sallymacfarlane@dev-elc-besu-teku-sepolia-dev-sally-test-6823:~$ grep -c B3Prop /var/log/besu/besu.log
961
sallymacfarlane@dev-elc-besu-teku-sepolia-dev-sally-test-6823:~$ grep -c B3Prop /var/log/besu/besu.log
962
sallymacfarlane@dev-elc-besu-teku-sepolia-dev-sally-test-6823:~$ grep -c B3Prop /var/log/besu/besu.log
964
sallymacfarlane@dev-elc-besu-teku-sepolia-dev-sally-test-6823:~$ grep -c B3Prop /var/log/besu/besu.log
1313

[fab-10]

should the log be at TRACE level in the code?

[macfarla]

should the log be at TRACE level in the code?

I did the same as we've done for noisy DNS messages etc. if you want to see the logs you can just take this out of your log4j config