Why not call this SupaPool? Supavisor is very BEAMie.

Question about telemetry.

These are the metrics emitted by Ecto:

- :idle_time - the time the connection spent waiting before being checked out for the query

- :queue_time - the time spent waiting to check out a database connection - :query_time - the time spent executing the query

- :decode_time - the time spent decoding the data received from the database

- :total_time - the sum of (queue_time, query_time, and decode_time)

To what extent are these metrics distorted by use of a Supavisor connection pooler? How could Supavisor compensate for that?