time-to-k8s: Benchmark k3d with etcd

[spowelljr]

Currently, in the time-to-k8s benchmark, we compare to k3d without etcd. Since both minikube and kind use etcd by default, we should enable etcd in k3d when benchmarking to have a better comparison between the tools.

[spowelljr]

dqlite was replaced with etcd with k3s-io/k3s#1770 and seems to be used by default.

To confirm I tried the following (multi-node):

% k3d cluster create
INFO[0000] Prep: Network
...
% k3d node create newserver --cluster k3s-default --role server
INFO[0000] Starting Node 'k3d-newserver-0'
% k3d cluster list
NAME          SERVERS   AGENTS   LOADBALANCER
k3s-default   2/2       0/0      true

So from my understanding etcd is being used when benchmarking k3d.

@medyagh @afbjorklund If you think otherwise let me know and I'd be happy to investigate.

Closing for now.