umask of containers created from python3 Dockerfile does not match Diamond default

For the case where:

- You create a containerised service
- Which mounts the Diamond filesystem
- And create files which are intended to be temporary, interleved with existing files

The current umask means those temporary files cannot be deleted by the user that created the directory that stores those files.
E.g. __pycache__ files made during an editable install of a library loaded from filesystem for blueapi, checked out by a member of dls_dasc

For blueapi (where we meet these requirements) we are [now setting the umask](https://github.com/DiamondLightSource/blueapi/pull/480/files): is anyone else going to meet those requirements and if so should this be configurable as part of the template, perhaps propagating into the Dockerfile?

首先檢查範本產生的 python3 Dockerfile，並將其 umask 與 Diamond 預設值進行比較。以 issue 中連結的 blueapi pull request 為例，然後定義應由哪項範本設定進行控制，並驗證產生的容器允許建立這些暫存檔案的使用者刪除它們。

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