TransactionalSession produces confusing log statements

[timbussmann]

Describe the suggested improvement

With #7675 new info logging was added when the outbox deduplicates a message. However, when using the transactional session, this log warning (e.g. Outbox duplicate detected for message 'f4cbed05-8fe2-47ef-b145-973ab39c900c'. Skipping handler execution) also appears on every single transactional session control message.
In this case, the "deduplication" is expected behavior and there is no handler invocation to be invoked anyway. This log message confuses users that upgrade from NSB 9 to 10 because suddenly they see log messages about deduplications which can't clearly be connected to the transactional session control message.

Describe the suggested solution

• lower the log level to Debug/Trace to only show up when intentionally trying to trace behavior
• skip the log for transactional session control messages

Describe alternatives you've considered

Additional Context

No response

[ramonsmits]

Another solution suggestion could be to ignore it for all control messages based on the NServiceBus.ControlMessage header

[ramonsmits]

@mauroservienti and I discussed this. We think a good first improvement to reduce the noise is to detect the NServiceBus.ControlMessage header, and if set use log level Debug, otherwise Info.

@timbussmann Do you consider that an improvement?

[timbussmann]

@ramonsmits sounds good enough to me. As a user, I just don't want to be confused by information about deduplication, when there is no deduplication of my own messages (but rather intended behavior of the tx session)