docs: improve developer experience and contract documentation

[Ryjen1]

This PR provides a comprehensive overhaul of the project's documentation and developer experience. It addresses the lack of detailed API references and integration guides for the core smart contracts, significantly lowering the barrier for new contributors and developers.

Key Changes

1. Comprehensive API Documentation

Updated docs/contracts.md with detailed technical references for:

• PropertyToken: ERC-721/1155 implementation and property-specific logic.
• ComplianceRegistry: KYC/AML and jurisdiction enforcement.
• PropertyBridge: Cross-chain multisig transfer mechanics.
• PropertyInsurance: Risk pool management and automated claims.
• IpfsMetadataRegistry: Managed access to off-chain documents.
• ZkCompliance: Privacy-preserving ZK-proof verification.

2. New Integration Tutorials

Added step-by-step guides in the docs/tutorials/ directory:

• Insurance Integration: Guide on risk assessment, policy creation, and claims.
• Cross-Chain Bridging: Guide on multisig bridge requests and execution.

3. Developer Support Resources

• Troubleshooting & FAQ: Solutions for common integration roadblocks.
• Best Practices Guide: Standards for security, gas optimization, and UI patterns.
• Onboarding Checklist: A streamlined setup process for new developers.

4. Architecture & Automation

• ADR System: Established an Architecture Decision Record (ADR) system in docs/adr/.
• CI/CD Automation: Added a GitHub Action to automatically verify and generate documentation documentation.

Closes #49

✅ Verification Results

• Verified the structural integrity of all new documentation files.
• Validated method signatures and data structures against the contract source code.
• Confirmed the GitHub Action workflow triggers correctly on push and PR events.
• Ran cargo doc locally to ensure no documentation build regressions.

[LaGodxy]

LGTM