Bootstrapping an agent from config fails silently on @veramo/cli@5.0.0

[Eengineer1]

Short description

While bootstrapping an agent, using the default config output from veramo config create, the agent object validation conditionals fall under the
unknown error while creating the agent from your config. Consider running `veramo config create` to generate a new configuration file, or to manually compare differences. block.
That means there's a hanging unresolved Promise, which is an obvious fix to convert to async propagate to whole stack and await Promise resolution.

Have you tried a similar setup / automated tests?
Fixes are simple, but need to be concise across the stack.

Let me know your thoughts.