feat: Business logic with ROI entering/leaving

[antoniomtz]

PR Checklist

• [x] Added label to the Pull Request for easier discoverability and search
• [x] Commit Message meets guidelines as indicated in the URL https://github.com/intel-retail/loss-prevention/blob/main/CONTRIBUTING.md
• [ ] Every commit is a single defect fix and does not mix feature addition or changes
• [ ] Unit Tests have been added for new changes
• [ ] Updated Documentation as relevant to the changes
• [ ] All commented code has been removed
• [ ] If you've added a dependency, you've ensured license is compatible with repository license and clearly outlined the added dependency.
• [ ] PR change contains code related to security
• [ ] PR introduces changes that breaks compatibility with other modules (If YES, please provide details below)

What are you changing?

• Added python extension to apply logic for the gvametadata to change roi_type to objects within the gvaattachroi (ROI).
• Published metadata to MQTT
• Added python business application to subscribe to MQTT and apply business logic for entering and leaving a ROI

Steps:

1. make build
2. make download-models (if you haven't done it before)
3. make INPUTSRC=https://github.com/openvinotoolkit/openvino_notebooks/raw/refs/heads/recipes/recipes/automated_self_checkout/data/example.mp4 PIPELINE_SCRIPT=yolov8s_roi.sh run-render-mode
4. Find the loss prevention container id and see the logs: docker logs -f

   Object bottle (ID: 4) entered the BASKET ROI.
   Current objects in ROI: {4: 'bottle'}

Issue this PR will close

close: #issue_number

Anything the reviewer should know when reviewing this PR?

Test Instructions if applicable

If the there are associated PRs in other repositories, please link them here (i.e. intel-retail/loss-prevention )