fix: revert to uid/gid 999

[rwaffen]

fixes #150

This might be breaking for all users who have used the newer images after #131 . We have mistakenly switched the uid/gid to 1001 and are now reverting it back to 999.

Checklist

I have:

• read the CONTRIBUTING.md document
• read and accepted the Developer Certificate of Origin document and added a Signed-off-by annotation to each of my commits
• read and accepted the AI Policy document and added Generated-by or Assisted-by annotations to each of my commits created with the help of an AI agent
• tested this code
• included documentation (including possible behaviour changes)
• documented the code
• added or modified regression test(s)
• added or modified unit test(s)

[rwaffen]

@bootc pls have a look

[bootc]

This looks very odd, what's that about? On Alpine, if the OPENVOX_USER_GID is 999, the OPENVOX_GROUP should be called ping?

[bootc]

Oh this is because of #150 (comment). Tricky. I wonder whether the answer is to just have different UID/GID numbers on Ubuntu vs Alpine?

[rwaffen]

When alpine and desired gid 999 use the name ping for the group. Because it already exists it is not required to create it. If not 999 use puppet as group name and create it.

[bootc]

Hi @rwaffen this PR definitely fixes the bug, but I do think that it might be better to have UID/GID 999 for the Ubuntu image like it has always been, and 1001 for Alpine as that's what that image started out with, plus it wouldn't conflict with the existing ping group. We'd need to clearly document that the difference exists but I think that would be perfectly fine, myself.

[rwaffen]

two different uid/gid, no. but document changes better, yes. use this approach, also no. will close this one here. maybe #157 is a better solution. 🤔