[Tracking]Windows issue with build config when config folder present in user plan

This is an issue with the Invoke-BuildDefaultConfig. Right now we are building the config files as part of the Invoke-BuildDefaultService. We are creating a config directory in the expected place but when Habitat's build service runs it attempts to run a Copy-Item "$PLAN_CONTEXT/config" $pkg_prefix -Recurse and there is already a config directory at $pkg_prefix. There are two ways to fix this in the user plan. The first is to delete the config folder. The second is to override the Invoke-BuildConfig and only copy the individual config files that are in the user's config directory. Instead, it would be better to move the config build to the Invoke-BuildDefaultConfig so that there is no conflict and still preform the recursive copy.