update ubuntu and python version

[ponceta]

update ubuntu and python version

[ponceta]

@sjib with postgresql >= 14, users won't be able to export their data.

I'm a postgresql 14 user and I have to export my data to migrate to VSA 2020.

Info: ili2pg-4.6.1-63db90def1260a503f0f2d4cb846686cd4851184
Info: ili2c-5.2.3-3ec7a10e9bacc87e149a14a7f11a6035e0481c69
Info: iox-ili-1.21.8-a6aee68136447c0616995e56888fa9c7ef362a77
Info: java.version 11.0.22
Info: user.name <runner>
Info: maxMemory 4091904 KB
Info: currentTime 2024-04-25 07:39:10
Info: dbschema <pg2ili_abwasser>
Info: dburl <jdbc:postgresql://127.0.0.1:5432/qgep_prod>
Info: dbusr <postgres>
org.postgresql.util.PSQLException: SCRAM authentication is not supported by this driver. You need JDK >= 8 and pgjdbc >= 42.2.0 (not ".jre" versions)
  SCRAM authentication is not supported by this driver. You need JDK >= 8 and pgjdbc >= 42.2.0 (not ".jre" versions)
Traceback (most recent call last):
  File "/home/runner/work/qgepqwat2ili/qgepqwat2ili/qgepqwat2ili/utils/various.py", line 50, in exec_
    proc = subprocess.run(
           ^^^^^^^^^^^^^^^
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/subprocess.py", line 571, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '"java" -jar "/home/runner/work/qgepqwat2ili/qgepqwat2ili/qgepqwat2ili/bin/ili2pg-4.6.1-bindist/ili2pg-4.6.1.jar" --schemaimport --dbhost "127.0.0.1" --dbport "5432" --dbusr "postgres" --dbpwd "postgres" --dbdatabase "qgep_prod" --dbschema pg2ili_abwasser --setupPgExt --createGeomIdx --createFk --createFkIdx --createTidCol --importTid --noSmartMapping --defaultSrsCode 2056 --log "/tmp/qgepqwat2ili/240425073909.ilicreate.log" --nameLang de /home/runner/work/qgepqwat2ili/qgepqwat2ili/qgepqwat2ili/ili/VSA_KEK_2019_2_d_LV95-20210120.ili' returned non-zero exit status 1.
Error: Process completed with exit code 1.

@3nids @domi4484 is the upgrade to the same dependancies as TEKSI wastewater a thing or would that be a huge refactoring and we would need a workaround for this?