v0.106.0

Added

• A GitLab relay holds one HTTP/2 connection to vk-hub. The relay's session and its requests
  share it, and the session authenticates them. The hub tells the relay when its reservations
  and jobs change and the relay fetches them, so no request is held open waiting. API-key
  clients, nodes, registries and relays of earlier releases stay on HTTP/1.1, as before.

Changed

• vk-hub's GitLab server pages show each relay with its runners. Runner tables fit the
  page, with scheduling details folded under each runner. A runner without a lane says its
  jobs are refused. Operators add and remove runners there; the Overview's relays link there.
• vk-gitlab needs a hub of this release: upgrade the hub first. Against an older hub it
  logs that the hub must be upgraded and takes no jobs from GitLab until it is.

Fixed

• Faster small reads from vk-registry. Clients reading many small objects over one
  connection, such as a build cache fetching entries, no longer wait about 40 ms extra
  per read.
• Faster small reads through a node's registry proxy. A job reading many small objects
  from the registry, such as a build cache, no longer waits about 40 ms extra per read.

Full Changelog: v0.105.1...v0.106.0