Replace subprocess.call() with check_call() in db.py to prevent silent failures

[guptapratykshh]

Description
I replaced subprocess.call with check_call in the database cli, ensuring that operations stop immediately and report errors if something goes wrong.

This PR fixes #3579

Notes for Reviewers

Signed commits

• Yes, I signed my commits.

[shlokgilda]

LGTM. Love the short, targeted PR. Added one suggestion to fix a docstring that was incorrect even before this change.

[sgoggins]

Waiting on Podman end to end test. The fundamental difference here is really the provision of detailed error messages in check_call both wait for a process to finish ... both return 0 if its all good ... I am not against this change, it seems better, but I think it will provide more information on failure rather than allow failure more quickly ...

[MoralCode]

check_call will raise an exception if something fails.
the way we use call here currently (not storing the results in a variable) effectively means we ignore failures

While this may lead to more crashes, they are crashes that would otherwise be maskes, so knowing about them is better

LGTM