On the seabolt requirement question...
As part of our long term plan to support as many languages, platforms and frameworks as possible with our official drivers, we're working towards a more modular architecture for our client-side libraries. Concretely, this means that drivers will be built on top of lower level libraries, called connectors.
Seabolt is one such connector, and has been built in C to ensure both great performance and broad compatibility. Connectors will in general encompass all protocol, type system and routing logic and will surface a "Connector API" on which drivers and other tooling can be built. Note that connectors are not intended for direct use by application software.
We do recognise that there are a small subset of platform configurations that might struggle to work with a C dependency library. This is obviously unfortunate for those in this position, but we do hope that the greater breadth of language support we can offer for the wider Neo4j community will offset these limitations. Over time, we may even be able to plug some of these gaps with pure language code, should we see a great enough need.
In terms of the extra steps required for the installation of a C dependency, we are also looking at ways to streamline this process. So watch this space!