DeviceStateAccessor: fix incorrect initial parameter propagation; restore ability to connect to devices

[lukaskollmer]

♻️ Current situation & Problem

Trying to connect (via SpeziDevices) to a peripheral doesn't work because the nearby.onChange state observer is sent an initial false value, which causes the peripheral to immediately get discarded after being discovered.

⚙️ Release Notes

• Fix issue that could prevent peripheral connection establishment

📚 Documentation

n/a

✅ Testing

n/a

📝 Code of Conduct & Contributing Guidelines

By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

• I agree to follow the Code of Conduct and Contributing Guidelines.

---

Note: this PR supersedes #52 (the difference being that this one is made from an repo-internal branch, which @PSchmiedmayer said was required for some of the actions to properly run)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.63%. Comparing base (4d64dfa) to head (dfe0618).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #53      +/-   ##
==========================================
+ Coverage   80.16%   80.63%   +0.47%     
==========================================
  Files         111      111              
  Lines        6053     6053              
==========================================
+ Hits         4852     4880      +28     
+ Misses       1201     1173      -28     

Files with missing lines	Coverage Δ
...th/Model/PropertySupport/DeviceStateAccessor.swift	59.02% <100.00%> (ø)
.../SpeziBluetooth/Modifier/AutoConnectModifier.swift	0.00% <ø> (ø)
...Bluetooth/Modifier/ScanNearbyDevicesModifier.swift	71.12% <ø> (ø)

... and 4 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4d64dfa...dfe0618. Read the comment docs.

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests

[PSchmiedmayer]

Thank you for the fix @lukaskollmer!

There are some unrelated SwiftLint errors that might come from an SwiftLint update, it would be amazing if you can also fix then and merge the PR after that, thank you!