Enable built-in bridge for testing

[jarhodes314]

Proposed changes

Enabling the built-in bridge when running robot tests to verify that #2879 has fixed the errors.

Types of changes

• [ ] Bugfix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
• [ ] Documentation Update (if none of the other choices apply)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

Checklist

• [ ] I have read the CONTRIBUTING doc
• [ ] I have signed the CLA (in all commits with git commit -s)
• [ ] I ran cargo fmt as mentioned in CODING_GUIDELINES
• [ ] I used cargo clippy as mentioned in CODING_GUIDELINES
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] I have added necessary documentation (if appropriate)

Further comments

[github-actions[bot]]

Robot Results

:white_check_mark: Passed	:x: Failed	:next_track_button: Skipped	Total	Pass %	:stopwatch: Duration
448	3	3	451	99.33	1h15m25.545439999s

Failed Tests

Name	Message	:stopwatch: Duration	Suite
Update tedge version from previous using Cumulocity	DeviceNotFound [RETRY] FAIL on 1. retry.	38.314 s	Tedge Self Update
Refreshes mosquitto bridge configuration	DeviceNotFound	41.182 s	Tedge Self Update
Test bridge service status up	DeviceNotFound	45.300 s	Service Monitoring