Currently, OpenLineage integration uses queryId as jobName field value:
https://github.com/trinodb/trino/blob/474/plugin/trino-openlineage/src/main/java/io/trino/plugin/openlineage/OpenLineageListener.java#L249

This is not very convenient, as each queryId is unique, and it also doesn't mean anything for end user. Instead, consider allowing user to set custom jobName using session variables:

SET SESSION openlineage-event-listener.job.name = 'myawesomejob';

X-Trino-Session: openlineage-event-listener.job.name=myawesomejob

Another option is to use X-Trino-Client-Info or X-Trino-Source, but it can contain data populated by low-level clients (Python client, HTTP client, JDBC driver and so on), and it usually used to identify particular client/software, not a session.