New LSF driver makes it difficult to see which komodo release is used with bhist

**Describe the bug**
With the old driver you could easily see which komodo version was used in the job using bhist/bjobs:
```
Job <581824>, Job Name , User , Project , Comman
d , Esub

```
with the new driver you get:
```
Job <582098>, Job Name , User , Project , Command <
/private/levje/ert/test-data/poly_example/poly_out/realiza
tion-9/iter-0/.lsf_submit_5igs03d0.sh /private/levje/ert/t
est-data/poly_example/poly_out/realization-9/iter-0>, Esub

```

**To reproduce**
Run poly with 2024.05 and 2024.06, and check the output of bhist for one job on each run.

**Expected behaviour**
Consider if it is possible to still provide the komodo version somehow.

Start by reproducing the issue with poly using Komodo 2024.05 and 2024.06, then compare the bhist or bjobs output for each run. Trace the new LSF driver's generated .lsf_submit script and command entry point; done means the job output still exposes which Komodo release was used.

Written by the indexing model from the issue text.