refactor!: Rework service names to conform to consistent naming

[lenny-goodell]

BREAKING CHANGE: Many sevice names have changed in order to conform with core-, support-, app- and device- naming standard. Impact should be minimal unless scripts have references to the old service names, rather than container names. Container name havent chnaged except for app-functional-tests' which is now edgex-app-functional-tests

closes #231 Signed-off-by: Leonard Goodell leonard.goodell@intel.com

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-compose/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 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

run make run ds-virtual Verify all service bootstrap and data is flowing from Device Virtual to App Rules Engine

[lenny-goodell]

@cherrycl , based on my searching of the TAF repo, this will not impact any tests except maybe backward compatible, which is not in scope for this release. I didn't find any scripts referencing the service names except for get-compose-file-backward.sh

[bnevis-i]

Testing affected by https://github.com/edgexfoundry/edgex-go/pull/4492, but after fix, nothing major seems to be broken.