OTEL tracing support

[NickBelhomme]

Is your feature request related to a problem? Please describe.
We are using pgx/v5: https://github.com/golang-migrate/migrate/tree/master/database/pgx/v5
This works great, however for our general usage we have attached an OTEL tracer to it.
https://pkg.go.dev/github.com/jackc/pgx/v5#ConnConfig.Tracer

    config, _ := pgxpool.ParseConfig("postgres://test:testpass@127.0.0.1:5432/test?sslmode=require&pool_max_conns=10&pool_max_conn_lifetime=20&pool_max_conn_idle_time=10")
    config.Tracer = otelpgx.NewTracer()
   conn, err := pgxpool.NewWithConfig(ctx, config)

currently looking at the migrate codebase I do not see an option to pass the tracer as a config option...

Describe the solution you'd like
A possibility to pass a tracer to the config

Why
It is useful to know how long some migration statements have run atomically .

[joschi]

Kind of related to #1132.

[joschi]

I got this pretty much working for most of the database drivers supported by golang-migrate.

Example screenshot of a trace running the SQLite example migrations:

@dhui It still needs some tuning here and there, but if the appetite is there, I can probably come up with a PR soon (-ish).

Although it kind of depends on #1132 being merged. 😅

[joschi]

Latest update:

• Source drivers are also instrumented now. While this doesn't make too much sense for the file driver (reading migrations from the local filesystem), it does for remote drivers such as github and gitlab.

• Database drivers have more attributes, such as the currently running migration.