fix: properly install dependencies in containers

docs/content/builder.md

@@ -15,7 +15,7 @@ repositories. After the image has been created, each repository returned by
 previously created image as a base. Each container goes through the following steps:
 
 1. The repository is cloned
-2. `makepkg --nobuild` is ran to update the `pkgver` variable inside
+2. `makepkg --nobuild --syncdeps --noconfirm` is ran to update the `pkgver` variable inside
    the `PKGBUILD` file
 3. A HEAD request is sent to the Vieter server to check whether the specific
    version of the package is already present. If it is, the container exits.

src/build/build.v

@@ -91,7 +91,7 @@ pub fn build_repo(address string, api_key string, base_image_id string, repo &db
 	commands := [
 		'git clone --single-branch --depth 1 --branch $repo.branch $repo.url repo',
 		'cd repo',
-		'makepkg --nobuild',
+		'makepkg --nobuild --syncdeps --noconfirm',
 		'source PKGBUILD',
 		// The build container checks whether the package is already
 		// present on the server