Considering using Opentelemetry Naming Conventions

[markhildreth-gravity]

Currently, gue attaches some span attribute when a job is being run. This is great, although the attributes do not match OpenTelemetry naming conventions.

For each multi-word dot-delimited component of the attribute name separate the words by underscores (i.e. use snake_case). For example http.response.status_code denotes the status code in the http namespace.

Thus job-id would be better named as job_id, etc.

[vgarvardt]

This is breaking change. I'll do it together with other BCs for the new major version once it is planned.