Fix websocket confirmation options handling

[gr0vity-dev]

This PR fixes an issue with the websocket confirmation message handling. Previously, the system would cache messages based solely on the include_block option, causing other subscriber options (like include_linked_account and include_sideband_info) to be ignored if another subscriber had already created a cached message.

Changes made:

• Removed the message caching mechanism that was causing options to be ignored
• Each subscriber now receives a message built specifically with their configuration options
• Simplified parameter naming for better readability
• Made options handling more consistent across the codebase
• Added a failing testcase that is passing by the removal of the cache

These changes ensure that all subscribers receive confirmation messages that correctly respect their individual option settings.

[gr0vity-dev-bot]

Test Results for Commit 0c6645a

Pull Request 4855: Results
Overall Status: ❌

Test Case Results

• ✅ 5n4pr_conf_10k_bintree: PASS (Duration: 109s)
• ✅ 5n4pr_conf_10k_change: PASS (Duration: 136s)
• ❌ 5n4pr_conf_change_dependant: FAIL (Duration: 576s)
• Log
• ✅ 5n4pr_conf_change_independant: PASS (Duration: 139s)
• ✅ 5n4pr_conf_send_dependant: PASS (Duration: 126s)
• ✅ 5n4pr_conf_send_independant: PASS (Duration: 118s)
• ✅ 5n4pr_rocks_10k_bintree: PASS (Duration: 107s)
• ✅ 5n4pr_rocks_10k_change: PASS (Duration: 174s)

Last updated: 2025-03-04 20:33:58 UTC

[gr0vity-dev]

This was previous code + testcase only:

Here is the run