[Security Solution] Fix rule snooze/unsnooze change history logging

[maximpn]

Epic: https://github.com/elastic/security-team/issues/12367 (internal)
Follow-up to: #267350
Related to: #269617

Summary

Fixed rule change tracking instrumentation for RulesClient snooze and unsnooze methods.

Details

snoozeRule and unsnoozeRule in RulesClient perform an OCC (optimistic concurrency control) update that only modifies snooze-related attributes. The saved object returned by that update contains only the updated partial attributes, not the complete rule document. Passing that partial object to logRuleChanges caused the change history record to be missing required rule fields, breaking change tracking for snooze and unsnooze actions.

The fix merges the original pre-update attributes with updatedRuleRaw.attributes so that logRuleChanges always receives a complete rule document.

Issues were discovered during e2e testing of the UI in #269617.

• snooze_rule.ts: Merge original attributes with updatedRuleRaw.attributes before passing the saved object to logRuleChanges.
• unsnooze_rule.ts: Same fix.
• snooze_rule.test.ts, unsnooze_rule.test.ts: Add test cases that verify logRuleChanges is called with the fully merged attributes.

[infra-vault-gh-plugin-prod]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[infra-vault-gh-plugin-prod]

Pinging @elastic/security-solution (Team: SecuritySolution)

[infra-vault-gh-plugin-prod]

Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management)

[pmuellr]

LGTM

[kibanamachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 7d4dd1f
• Build duration: 67 mins

Failed CI Steps

• FTR Configs #81
• FTR Configs #105
• Serverless Investigations - Security Solution Cypress Tests #3

Metrics [docs]

✅ unchanged

History

• 💔 Build #450344 failed b8b4d67
• 💚 Build #450278 succeeded 3c7481e

cc @maximpn