glib: configure with `$PYTHON` as python

This take another approach at c5cd4e06 (component/glib: set --with-python
to generate scripts with slapos python, 2022-09-20) because this python
might exceed the limit of shebang lines, that change was bad because it
brought back the problem that we fixed in 6acdc8ca (glib: put the expected
python in $PATH, 2019-12-18)

Now that component/defaults.cfg set the ${python:location}/bin in $PATH,
we can assume that python is always in $PATH. The problem with python3
software is that python3 does not install a "python" binary, only python3,
so we can use the $PYTHON environment variable which will be set to
python2 or python3 and that in both cases this will be a valid python
interpreter.

This re-applies 7581b668 (component/glib: remove bad file bin/gtester-report
after compilation, 2020-08-07) because with this approach that script's
shebang is just #!python3
12 jobs for fix/glib-python (queued for 1 second)
Status Job ID Name Coverage
  External
running Cloudooo.UnitTest-Master

20898:01:25

running ERP5.StandaloneDeploymentScriptTest-Debian.Buster.Master

20898:01:51

running ERP5.StandaloneDeploymentScriptTest-Debian.Stretch

20898:01:02

running SlapOS-Master.StandaloneDeploymentScriptTest-Debian.Buster

20898:01:00

running SlapOS.Eggs.UnitTest-Master.Python2

20898:00:56

running SlapOS.Eggs.UnitTest-Master.Python3

20898:01:06

running SlapOS.KVM.ResilienceTest-Master

20898:00:40

running SlapOS.SlapRunner.ResilienceTest-Master

20898:01:33

running SlapOS.SlapRunner.ResilienceTest-Master.ERP5

20898:01:09

running SlapOS.SoftwareReleases.IntegrationTest-Jerome.Work

20898:02:26

running Wendelin.StandaloneDeploymentScriptTest-Debian.Buster

20898:01:21

running Wendelin.StandaloneDeploymentScriptTest-Debian.Stretch

20898:01:47