Improve appearance of `dbc search` output in narrow terminals

[ianmcook]

The dbc search output wraps in narrow terminals, which looks bad and is hard to read. As the number of drivers grows, this becomes more of a problem. Also, the driver descriptions in the dbc search output are long and contain a lot of superfluous information. Let's reconsider how we present the dbc search output to fix these issues.

[amoeba]

Re: wrapping. It's pretty common for CLI programs to produce wide enough output they soft-wrap. Our output is currently ~130 chars wide which is wide but not unusually so.

I'm linking the discussion in #222 for reference. I think the thing we didn't take on in that discussion was removing some of the redundancy from the descriptions. Could we revisit that? I'd propose this as new output,

# column           20                  40                  60                  80
bigquery             Driver for Google BigQuery         [installed: user=>1.11.2]
databricks           Driver for Databricks              [installed: user=>0.1.2] 
datafusion           Driver for Apache DataFusion       [installed: user=>0.24.1]
duckdb               Driver for DuckDB                  [installed: user=>1.5.2] 
exasol               Driver for Exasol                  [installed: user=>0.12.0]
flightsql            Driver for Apache Arrow Flight SQL [installed: user=>1.11.0]
mssql                Driver for Microsoft SQL Server    [installed: user=>1.3.1] 
mysql                Driver for MySQL                   [installed: user=>0.3.1] 
postgresql           Driver for PostgreSQL              [installed: user=>1.11.0]
redshift             Driver for Amazon Redshift         [installed: user=>1.2.1] 
snowflake            Driver for Snowflake               [installed: user=>1.10.3]
sqlite               Driver for SQLite                  [installed: user=>1.11.0]
trino                Driver for Trino                   [installed: user=>0.3.1] 
oracle     [private] Driver for Oracle Database         [installed: user=>0.5.1] 
teradata   [private] Driver for Teradata                [installed: user=>0.1.1] 

If we did this, the only change we'd need to make would be on the CDN.

[amoeba]

@ianmcook suggested adding structured metadata to the CDN index (vendor, publisher) and having dbc search try to use this instead or over the description.