Docker image size is blowing up

When comparing the last few releases in
https://console.cloud.google.com/gcr/images/kaggle-images/GLOBAL/python
it is quite noticeable that recently there has been a sudden increase in the docker image size, e.g. from virtual size 6.2 GB of `v125` to virtual size of 8.3 GB of `v129`, i.e. a 34% increase.

When uncompressed, docker reports that `v125` results in a 19 GB container, while `v129` results in a 23 GB container, i.e. a 21% increase.

I noticed this while running (the heaviest of) my workflows on GitHub Actions, randomly getting errors like
```
System.IO.IOException: No space left on device : '/home/runner/runners/2.302.1/_diag/Worker_20230304-204952-utc.log'
```
While surely the amount of disk space that GitHub offers is not your responsibility, you may still want to check if there is any way to keep the size of the docker image under control, and if possible keep it from growing at this rate any further.

首先，使用連結的 Google Container Registry 映像比較 v125 和 v129 的 Docker 映像層與建置歷程。找出哪些版本變更造成了增長，然後驗證後續映像在保留映像現有內容的同時，不再以所回報的速率增長。

由索引模型根據 Issue 內容生成。