fix:[#1525] handle container creation failure

[jardon]

distrobox fumbles the error handling for container creation. the exit command is nested inside of the creation success conditional statement. this PR adds an else statement and handles the subprocess error by passing it up

changes:

• print error message and exit with subprocess return code

here's the output now that the error is handled:

jardon@lagann:~/Projects/distrobox$ ./distrobox create --additional-flags jammy      --image docker.io/library/ubuntu:jammy --name apx-test --no-entry --yes --pull 
Trying to pull docker.io/library/ubuntu:jammy...
Getting image source signatures
Copying blob 857cc8cb19c0 skipped: already exists  
Copying config 53a843653c done   | 
Writing manifest to image destination
53a843653cbcd9e10be207e951d907dc2481d9c222de57d24cfcac32e5165188
Creating 'apx-test' using image docker.io/library/ubuntu:jammy	Resolving "jammy" using unqualified-search registries (/etc/containers/registries.conf)
Trying to pull docker.io/library/jammy:latest...
Error: initializing source docker://jammy:latest: reading manifest latest in docker.io/library/jammy: requested access to the resource is denied
 [ ERR ] failed to create container.
jardon@lagann:~/Projects/distrobox$ echo $?
125

Closes #1525

[jardon]

@89luca89 you mind looking at this? yes, it stemmed from an error with apx but it shows that a non-zero exit with podman resulted in a 0 exit for distrobox

[softmoth]

This looks good to me. NOTE: removing the exit $? within the if branch is OK, because it would be the last statement executed in the script and is therefore redundant. However, it might be best to leave it in just as an explicit indicator that "Hey, we rely on this exit status here!", and to have a nice symmetry between the if and else clauses.

[89luca89]

Thanks @jardon and @softmoth for looking into it!