Component status can stuck in starting/stopping status on heartbeat lost

Now server sets components statuses to UNKNOWN and saves last actual state on heartbeat lost. After agent re-registering server restores saved state, but in case "in progress" state request is already aborted and agent status updates can not be applied. Agent should always send component statuses after registering, not only on status changes. Also last actual state logic should be removed.