Improve dbt command execution logs to troubleshoot None values

[tatiana]

Recently, an Astronomer customer reported they were facing the following error while trying to run Cosmos and couldn't troubleshoot it (the screenshot was a courtesy by the customer, when using Cosmos 1.7.1):

The following log line was sub-optimal since it errored if the value was None:

astronomer-cosmos/cosmos/dbt/graph.py

Line 136 in 43998d2

logger.info("Running command: `%s`", " ".join(command))

To change just the log line was not enough since the None would also break the subprocess command execution (screenshot also by the customer when trying 1.8.0a1):

By changing both, the source problem became evident to the customer (screenshot by the customer when trying 1.8.0a2):

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.24%. Comparing base (110fb07) to head (9537fce).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1392   +/-   ##
=======================================
  Coverage   96.24%   96.24%           
=======================================
  Files          67       67           
  Lines        4051     4052    +1     
=======================================
+ Hits         3899     3900    +1     
  Misses        152      152           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.