feat!: load common configuration from config provider

[FelixTing]

fix: #481

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/device-sdk-c/blob/main/.github/Contributing.md

PR Checklist

Please check if your PR fulfills the following requirements:

• [ ] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
• [x] I am not introducing a new dependency (add notes below if you are)
• [ ] I have added unit tests for the new feature or bug fix (if not, why?)
• [x] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
• [ ] I have opened a PR for the related docs change (if not, why?)

Testing Instructions

Non-secure mode testing

1. From the latest compose builder run make run no-secty.
2. Run device-random example (/src/c/examples/random) with -cp=consul.http://localhost:8500 --registry arguments.
3. Verify that the device-random configuration has been written to Consul K/V Store.
4. Update Writable configuration for device-random and core-common-config-bootstrapper on Consul K/V Store, and then verify if it takes effect.

Secure mode testing

1. From the latest compose builder, modify add-security.yml to add secret store token and registry ACL role for device-random, and then run make run.
2. Set environment variable EDGEX_SECURITY_SECRET_STORE to true and run device-random example (/src/c/examples/random) with -cp=consul.http://localhost:8500 --registry arguments.
3. Verify that the device-random configuration has been written to Consul K/V Store.
4. Update Writable configuration for device-random and core-common-config-bootstrapper on Consul K/V Store, and then verify if it takes effect.

New Dependency Instructions (If applicable)