GPU-celery Dockerfile python version update needed

[homework36]

I still don't understand how Docker Hub build test works (as part of CI). For example, my latest PR #1182 successfully passes all checks but after it's merged into develop, the Docker Hub webhook build fails. I also don't know when the image build will be triggered.

If we click on "details" we get

"error": "Our service is temporarily unavailable. We'll be back soon!"

Update: We do have new images built on Docker Hub with tag nightly as expected, and I have used those new images to test locally and then update staging. There seems no problem. The Docker Hub image build failure happens to the webhook, which I believe is the test.
According to line 38 in hook.py, we get ddmal/docker-webhook:rodan-pass-{SOMETHING} after we can successfully push gpu-celery, postgre, nginx, and iipsrv images. In fact, we do miss newly built images for those on our Docker Hub.

[homework36]

Error message for gpu-celery build failure on Docker Hub for recent PR (link):

This script does not work on Python 3.7. The minimum supported Python version is 3.8.

We need to update versions for gpu-celery in the relevant Dockerfile.
Because we don't update most GPU jobs that frequently, there is probably some time for us to test and update.

[homework36]

GPU Dockerfile has been fixed but the newly built iipsrv does not work and returns this error:

2024-07-08 13:10:47 Error loading shared library libwebpmux.so.3: No such file or directory (needed by /fcgi-bin/iipsrv.fcgi)
2024-07-08 13:10:47 Error relocating /fcgi-bin/iipsrv.fcgi: WebPMuxAssemble: symbol not found
2024-07-08 13:10:47 Error relocating /fcgi-bin/iipsrv.fcgi: WebPMuxSetImage: symbol not found
2024-07-08 13:10:47 Error relocating /fcgi-bin/iipsrv.fcgi: WebPMuxSetChunk: symbol not found
2024-07-08 13:10:47 Error relocating /fcgi-bin/iipsrv.fcgi: WebPNewInternal: symbol not found
2024-07-08 13:10:47 Error relocating /fcgi-bin/iipsrv.fcgi: WebPMuxDelete: symbol not found

The exactly same Dockerfile was used.
I will work on this and fix it on the same branch and make one PR.
Related: #1119

Sorry, I didn't realize my branch was created based on master, which does not have the latest commits. I deleted the previous branch and created a new one.