chore: publish tag to dockerhub as latest as well

fix: make sure tags are fetched in buildkite

Refs:
buildkite/agent#338
buildkite/agent#1537

feat: add DockerHub builds [VAX-542] (#57)

Publish tagged commits as images to docker hub

Co-authored-by: define-null <vasilii@electric-sql.com>

VAX-490: Materialize transaction only when the cache has been updated…

… up to global op id. (#55)

Fix in vx wal stream - previously global operation id check was always passing
if snapshot was stale. That has been fixed in vx_server application.

When receiving transactions from remote DCs global value of operation was not
updated, leading to non-monotonically increased values. Thus relying on that
value in vx_server was leading to errors. This was fixed, so that for remote dcs
operation number is combination of the monotonically increasing value within
local dc (global) and monotonically increasing value for transactions originated
in remote dc (local).

Improve DC and InterDC Functionality (#408)

* Test case for issue #400 
* Removed stable riak metadata and improved create dc.
* Changed level of pending changes log messages
* Added a better named function to add nodes to a current dc
* Changed description and test case for dc descriptors. Fixed #400
* Reverted handle call for periodic updates, not needed
* Bumped to version 0.2.2
* Reduced severity of log message for missing external_descriptors
* Update include/antidote.hrl
* Added leave_dc functionality

We maintain our own dc id based on the riak_core_ring:cluster_name/1 command.
Riak maintains the cluster name itself, and contrary to the comment in dc_utilities,
it is restored on fail and restart correctly, even if all nodes fail at the same time.
This caused errors in maintaining the ring members after simplifying the create_dc function
and errors in shard count meta data. Switching back to the riak internal meta data
(which is managed and updated by riak_core anyway) fixes these issues.
The create_dc simplification also improved joining an empty cluster significantly (10 seconds for 8 shards).
This is also work towards being able to add/remove nodes dynamically to scale after some time elapsed.

Co-Authored-By: Peter Zeller <p_zeller@cs.uni-kl.de>

Redirected slave logs to ct master logs

Cluster management pb fix (#372)

* downgrade lager because of logging problems
* change test setup

- forking ct_slave because it cannot be configured as I want it to
- now sets the working directory for slaves, so lager logs to the
correct directory
- standard output of slaves is written to the ct-log and to stio.log
file, which should make debugging easier
- protocol buffer process now also reports stacktrace to client
* also testing connect_to_dcs
* use different node names for cluster management test
* Adapted to cleanup of antidote_pc_codec
* Upgraded to lint v0.1.10 which is checking more things.
* Few fixes for the connection descriptors
* Encoding ignore in pb_client
* Updating the dependencies

fixed

Tag for hydra branch start