Describe the bug
When a new instance of CWA is created without an existing app.db, the app.db is being created as root. When PUID is set in Environmental Variables the container is unable to start because it is unable to write to the app.db after creating it. I'm assuming the new cwa-init function isn't using the ownership Env Vars when creating the app.db.

To Reproduce
Steps to reproduce the behavior:

1. Create a fresh instance of CWA with PUID/PGID set, without an existing app.db
2. Check logs
3. Check ownership of app.db

Expected behavior
Fresh install of CWA starts

Configuration:

• OS: Ubuntu Server
• Hardware: x86 server
• Version 3.0.2

Additional context
Changing the ownership of app.db and restarting the container allows the initial startup to complete as expected.