Improve the Gitaly weight assigner to take CPU utilization into account

Currently, our Gitaly Shard Weight Assigner only disk space into account.

This means that we are not evenly distributing traffic across Gitaly nodes, some nodes are running hot while others receive less traffic.

We could improve this by taking CPU utilization into account. Perhaps we can reuse saturation metrics for this?