Why

ConfigBuilder::build performs a large amount of async config loading. Leaving that entire future on the caller stack makes config startup more fragile on small runtime worker stacks.

What changed

• keep ConfigBuilder::build as a thin wrapper that boxes the config-loading future before awaiting it
• move the existing implementation into a private build_inner method so the large async state machine lives on the heap instead of the runtime thread stack

Testing

• Not run locally