[WIP] [DONT MERGE] Upgrade tooz, re-enable service registry registration by default

[Kami]

This pull request updates tooz dependency to our fork - https://github.com/openstack/tooz/compare/master...StackStorm:etcd3_driver_fixes?expand=1.

Latest version does contain some group related functionality in etcd3 and etcd3+http driver, but it's partial and broken.

I've fixed various issues in our fork and I also plan to submit changes upstream (but it might take a while to get them merged and new version releases) so we need to use our fork for now.

There are some more issues I need to fix there.

NOTE: For this to work in stackstorm-ha, we need to ensure etcd >= 3.0.0 is installed and used. In addition to that, we need to use etcd+http://localhost driver there.

[Kami]

It looks like group membership functionality is quite badly broken in those two drivers and will need more work.

[arm4b]

Tracking & cross-linking corresponding issue in stackstorm-ha for switching etcd2 -> etcd3: StackStorm/stackstorm-k8s#58. We'll try to migrate to v3 in next few days.

[arm4b]

Per StackStorm/stackstorm-k8s#61 (review), looks like we'll also need etcd3gw pip dependency to make etcd3+http entrypoint (https://docs.openstack.org/tooz/latest/user/drivers.html#etcd3-gateway) work out of the box

[stale]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically marking is as stale. If this issue is not relevant or applicable anymore (problem has been fixed in a new version or similar), please close the issue or let us know so we can close it. On the contrary, if the issue is still relevant, there is nothing you need to do, but if you have any additional details or context which would help us when working on this issue, please include it as a comment to this issue.

[stale]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically marking is as stale. If this issue is not relevant or applicable anymore (problem has been fixed in a new version or similar), please close the issue or let us know so we can close it. On the contrary, if the issue is still relevant, there is nothing you need to do, but if you have any additional details or context which would help us when working on this issue, please include it as a comment to this issue.