fix: Remove attempt to connect to the MessageBus from trigger

This is now handled by the MessageBus bootstrap handler.

closes #1479

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

PR Checklist

Please check if your PR fulfills the following requirements:

[x] 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?) N/A existing suffice
[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?) N/A

build ASC with NATS capability locally (non-docker) with this branch of the SDK

Build edgex-go Docker with NATS capability Build Device Virtual Docker for NATS Run non-secure EdgeX stack with NATS Bus

make run ds-virtual no-secty nats-bus

Stop app-rules-engine container Verify app-rules-engine no longer fails with "already connected to NATS" message Run ASC with NATS locally

./app-service-configurable -cp -d -p rules-engine

Verify app-rules-engine (ASC) bootstraps w/o error

Run non-secure EdgeX stack with REDIS Bus Stop app-rules-engine container

make run ds-virtual no-secty app-dev

Run ASC with NATS locally

./app-service-configurable -cp -d -p rules-engine

Verify app-rules-engine (ASC) bootstraps w/o error

Run non-secure EdgeX stack with MQTT Bus Stop app-rules-engine container

make run ds-virtual no-secty app-dev mqtt-bus

Verify app-rules-engine bootstraps w/o error