feat: heartbeat for robot-location can_reach relation and cron done

[appmdev]

Description

Endpoint for Heartbeat for robot-location CAN_REACH relation done with additional cron job to delete 3 min incative relations.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• [x] New feature (non-breaking change which adds functionality)

What has been changed?

• Feature: From CentralAPI can be created and deleted relation CAN_REACH for heartbeat

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• [x] Test A: Two correct locations were provided with existing robot id, two relations were created respectively
• [x] Test B: One of the location was updated after 2 minutes, and waited for another 2 minutes, where older then 3 minutes relation was deleted.
• [x] Test C: Two correct locations were provided one existing and another inexisting with existing robot id, one relations was created respectively.
• [x] Test D: Relation was deleted using endpoint via postman, Relation disapeared from graph
• [x] Test E: The relation and robot had more then one different relations. From endpoint using postman was deleted relation, result from graph disapeared only CAN_REACH relation, other remained untouched.

Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my code
• [x] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [ ] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes