feat: Core Keeper changes based on OpenZiti changes

[jackchenjc]

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

New Dependency Instructions (If applicable)

[cloudxxx8]

LGTM

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 55.09%. Comparing base (7073930) to head (614d19a).

Files	Patch %	Lines
bootstrap/registration/registry.go	0.00%	1 Missing ⚠️

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #723      +/-   ##
==========================================
- Coverage   55.12%   55.09%   -0.03%     
==========================================
  Files          32       32              
  Lines        2705     2706       +1     
==========================================
  Hits         1491     1491              
- Misses       1112     1113       +1     
  Partials      102      102              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[dovholuknf]

@cloudxxx8 / @jackchenjc, this has an unintentional side-effect of breaking device-virtual. Strictly speaking this also should not be necessary as the zitified transport is configured with fallback, meaning if it can't dial a zitified endpoint, it should fallback to using an underlay dialer.

I'm sure this was a problem somewhere/somehow, but can I work with you to figure out why??