feature/spatial-analytics-documentation - Add spatial analytics developer guide

[rawatts10]

📝 Description

This PR adds comprehensive developer documentation for working with SceneScape's spatial analytics data, focusing on ROIs (Regions of Interest) and Tripwires. The documentation provides complete guidance for building applications that consume spatial analytics events from SceneScape's sensor-agnostic platform.

What was changed:

• Added working-with-spatial-analytics-data.md (872 lines) - complete developer guide for spatial analytics
• Added sample_region_tripwire.png - visual example from Intel HQ Santa Clara parking lot

Why it was needed:

• Developers need comprehensive documentation to understand and consume spatial analytics events
• Real-world examples help developers understand practical deployment scenarios
• The sensor-agnostic architecture benefits were not well documented
• Authentication patterns for different deployment scenarios needed clarification

How the changes add value:

• Provides complete tutorial with Python and JavaScript examples ready to run
• Documents all event data structures with detailed field descriptions
• Explains multi-sensor advantages and sensor-agnostic architecture
• Includes Intel HQ parking lot example showing real-world ROI and tripwire deployment

✨ Type of Change

Select the type of change your PR introduces:

• 🐞 Bug fix – Non-breaking change which fixes an issue
• 🚀 New feature – Non-breaking change which adds functionality
• 🔨 Refactor – Non-breaking change which refactors the code base
• 💥 Breaking change – Changes that break existing functionality
• 📚 Documentation update
• 🔒 Security update
• 🧪 Tests
• 🚂 CI

🧪 Testing Scenarios

Describe how the changes were tested and how reviewers can test them too:

• ✅ Tested manually
  • Verified all code examples work with SceneScape deployment
  • Tested Python scripts (discover.py, listen.py) with live MQTT events
  • Validated JavaScript web example with WebSocket MQTT connection
  • Confirmed image rendering and file structure
• 🤖 Ran automated end-to-end tests

Manual Testing Details:

• Environment setup instructions tested on Ubuntu
• REST API examples validated against SceneScape deployment
• MQTT authentication patterns verified for both WebSocket and direct protocols
• All tutorial examples run successfully and produce expected output
• Documentation formatting and internal links verified

✅ Checklist

Before submitting the PR, ensure the following:

• 🔍 PR title is clear and descriptive
• 📝 For internal contributors: If applicable, include the JIRA ticket number (e.g., ITEP-123456) in the PR title. Do not include full URLs
• 💬 I have commented my code, especially in hard-to-understand areas
• 📄 I have made corresponding changes to the documentation
• ✅ I have added tests that prove my fix is effective or my feature works

Additional Notes:

• This is purely a documentation enhancement with working code examples
• All examples include detailed explanations and are ready for immediate use by developers
• The Intel HQ example provides real-world context that makes the concepts immediately understandable
• No configuration or infrastructure changes included

[kblaszczak-intel]

It's is a really comprehensive article. I'd love to read it all and carefully but I can do it after it's merged. At first glance, it looks really solid.

[saratpoluri]

The document needs to be in the toctree. Please also consider in which document it can go as a reference link.