TransactionsHandle propagation commands should not adhere to caching

[Parikalp-Bhardwaj]

Closes #12033

Description:
This pull request addresses the issue where manual propagation commands in TransactionsHandle were adhering to caching, preventing forced broadcasts. The following changes have been made:

• Added PropgateKind Enum:
  Introduced a PropagateKind enum with variants Basic and Forced to control caching behavior during transaction propagation.

• Modified Propagation Methods:
  Updated methods such as propagate_full_transactions_to_peer, propagate_hashes_to, and propagate_transactions to accept a PropgateKind parameter.

• Updated Manual Propagation Commands:
  In the on_command method, manual propagation commands now use PropgateKind::Basic to bypass the cache, allowing forced broadcasts.

• Ensured Regular Propagation Respects Cache:
  Regular propagation commands continue to use PropgateKind::Forced, maintaining the caching mechanism to optimize network usage.

• Updated Tests:
  Modified existing tests and added new ones to cover scenarios with both cache policies, ensuring that the caching behavior is as expected.

@mattsse Please review the changes and let me know if any adjustments are needed.

[mattsse]

cool, functionally this is correct.

only have style nits

[mattsse]

I'd like to rename this slightly to something like

enum PropgateKind {
  /// Default propgation mode, filters out txs that we already sent or received
  Basic,
  /// Always propagate, even if we already sent or received the txs.
  Forced,
}

[mattsse]

ah, I see we already have an enum that is used with that name.

we need a new enum just for this, with the two variants. this should not change the existing enum

[Parikalp-Bhardwaj]

@mattsse done, Created a new enum PropgateKind with the two variants.