Add core-common-config-bootstrapper to Run EdgeX Natively documentation

[gerardkr]

📚 Docs or Wiki Bug Report

Description [REQUIRED]

https://docs.edgexfoundry.org/3.1/getting-started/native/Ch-BuildRunOnLinuxDistro/ starting about 1/4 down the page with "Run EdgeX". These instructions suggest how to run EdgeX natively. At a high level, the steps should be: 1 - Start redis 2 - Start consul 3 - (Missing) run core-common-config-bootstrapper 4 - Starting up all the remaining, individual services. However, step 3 (Run core-common-config-bootstrapper) is not currently mentioned. A brief paragraph should be added to cover the need for step 3. ## 🔬 Minimal Reproduction ### What's the affected URL? [**REQUIRED**] https://docs.edgexfoundry.org/3.1/getting-started/native/Ch-BuildRunOnLinuxDistro/ ### Expected vs Actual Behavior . Developers need to be instructed to run core-common-config-bootstrapper when running everything natively. ## 📷Screenshot

🔥 Exception or Error

If core-common-config-bootstrapper is not run, multiple Warning messages are generated about missing values.  Here is one example: 

level=WARN ts=2023-11-27T02:29:09.647411Z app=core-metadata source=config.go:1056 msg="did not get boolean from config provider for edgex/v3/core-common-config-bootstrapper/IsCommonConfigReady: strconv.ParseBool: parsing "": invalid syntax"

🌍 Your Environment

. Chrome Version 119.0.6045.159 (Official Build) (x86_64)

[lenny-goodell]

@gerardkr , Thanks!

[lenny-goodell]

@gerardkr , this is now fix for Napa and main. https://docs.edgexfoundry.org/3.1/getting-started/native/Ch-BuildRunOnArm32/#run-edgex