Support hikari-cp out of the box?

**Is your feature request related to a problem? Please describe.** [hikari-cp](https://github.com/tomekw/hikari-cp) is a long-standing wrapper for HikariCP that provides the convenience of kebab-case keywords in the options hash map, as well as providing some utility functions. `next.jdbc`'s built-in support for HikariCP relies on headlessCamelCase keywords in the options hash map and provides only a basic API for creating the pool, dependent on `clojure.java.data`'s behavior. **Describe the solution you'd like** It would be nice if `next.jdbc.connection/->pool` could support `hikari-cp` directly. Perhaps the `clazz` name could be a string (or symbol) for `hikari-cp` -- or perhaps just a fn, so users could pass `hikari-cp.core/make-datasource` directly? **Describe alternatives you've considered** The fn approach would be more generic but `->pool` would devolve to simply calling it so it doesn't buy much. Passing `"hikari-cp"` or `'hikari-cp` would be cleaner, and `next.jdbc` could call `requiring-resolve` to get the underlying fn and verify it is on the classpath. **Additional context** Any thoughts on this @tomekw?