test: integration suite for bridge <-> oracle cross-contract resolution

[Dataguru-tech]

PR 1: Introduces a CI workflow to run formal verification on selected smart contracts using Kani or cargo-verifier. The verification covers critical security invariants, including balance conservation, access-control role membership, and oracle staleness bounds, helping detect correctness issues early in the development lifecycle.

PR 2: Adds an end-to-end integration test (tests/integration_bridge_oracle.rs) that validates the bridge and oracle interaction flow, covering oracle updates, bridge attestation, and cross-chain verification to ensure correct cross-contract behavior.

PR 3: Introduces property-based fuzz tests using proptest for the property token contract. The suite validates edge cases including zero-amount transfers, self-transfers, transfers of non-existent tokens, and default recipient transferTo hook behavior to improve contract robustness.

PR 4: Adds an automated release workflow that generates CHANGELOG.md from Conventional Commit messages using git-cliff or conventional-changelog. The workflow is integrated into .github/workflows/release.yml to streamline release documentation and maintain consistent changelogs.

Closes #649
Closes #648
Closes #647
Closes #646

[drips-wave]

@Dataguru-tech Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[nanaf6203-bit]

🙌 Real safety win here — Kani harnesses for balance conservation / access control / oracle staleness + a bridge↔oracle integration suite gives us much better coverage. Closes #649, #648, #647, #646. Merging!