Sidecar controller should populate service annotations independently

[czeslavo]

Context

Currently, the sidecar controller populates both node Service annotations (hostID and token ring hash) at once. That means that even if it could already populate the hostID annotation, but there's no token ring hash available yet, it doesn't populate either of those.

The goal of this issue is to make the logic responsible for populating hostID and token ring hash annotations independent so that they do not block each other.

Acceptance criteria

• Sidecar controller populates the node Service's internal.scylla-operator.scylladb.com/host-id annotation once the host ID is available, without waiting for the token ring
• Sidecar controller populates the internal.scylla-operator.scylladb.com/current-token-ring-hash annotation once the token ring for the local node is available

[scylla-operator-bot]

The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 30d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out

/lifecycle stale

[rzetelskik]

/remove-lifecycle stale
/triage accepted