resolveConfig should likely be made async at this stage and refactor the call sites calling it.
Async config resolution will support potentially faster loading in some environments (vscode, MCP) that can do other tasks before the config is needed/ready and better support config loading and other plugin needs.
This task should also look at the utility of the loadConfig SDK function. This may no longer be of use and all call sites might be able to change to resolveConfig, our main configuration function