Improve error message when a task depends on another task that cannot be resolved

[NiklasRosenstein]

Example:

from kraken.std.cargo import cargo_publish, cargo_login, cargo_registry, cargo_sync_config

cargo_registry("local", "http://localhost:35504/", read_credentials=("username", "password"), publish_token="xxx")
# cargo_sync_config()
cargo_login()
cargo_publish(registry="local")

Because cargo_login() hardcodes a dependency on :cargoSyncConfig, running kraken in this project results in:

$ kraken query tree --all -v
[02/27/24 13:23:18] ERROR    No task matched the selector ':cargoSyncConfig'. Not finding what you're looking for? You can use the 'kraken query tree --all' command to list every available task.                       main.py:588
Exit code: 1 (status: FAILED)

For one, we don't enrich the error with additional contextual information (e.g. which task was requiring this task?) and we also drop the exception traceback in kraken.core.cli.main.on_exception() (under the assumption that we'd only get this error when passing a bad task name via the CLI in which case the error message is not-so-not-obvious).