feat: quality of service

[Tjemmmic]

Overview

• Implements heartbeat logic and storage for Blueprints in Services pallet

[drewstone]

So if we're requiring operators to submit heartbeats then we ought to consider what happens when enough heartbeats are missed. What does the ImOnline pallet do @1xstj that we can maybe copy here? We can be generous and allow heartbeats to be missed but if we have like 10 heartbeats in a row missed or <90% uptime in a session then we consider that bad.

Continuing on the last point, we could leverage this to create some sort of SLA guarantee or slash occurs. Would the customer request a certain SLA and cause the interval of heartbeats to change for specific service? I think @Tjemmmic it's worth considering that we might even want fine-grained intervals and other config per service.

Great start nonetheless!