fix(ble): Modify size of rssi in BLEAdvertisedDevice.toString()

[Oros42]

Description of Change

In BLEAdvertisedDevice.toString(), modify the rssi size to avoid truncation.

Why

When rssi == -102, it print :
Advertised Device: Name: , Address: 12:34:56:78:9a:bc, manufacturer data: 123456789, txPower: 12, rssi: -10
because snprintf add \0 at the end of the array.
So the size of -102\0 is 5 not 4.

[github-actions]

	Warnings
⚠️	Some issues found for the commit messages in this PR: the commit message "Fix size of rssi in toString()": summary looks empty type/action looks empty Please fix these commit messages - here are some basic tips: follow Conventional Commits style correct format of commit message should be: <type/action>(<scope/component>): <summary>, for example fix(esp32): Fixed startup timeout issue allowed types are: change,ci,docs,feat,fix,refactor,remove,revert,test sufficiently descriptive message summary should be between 10 to 72 characters and start with upper case letter avoid Jira references in commit messages (unavailable/irrelevant for our customers) TIP: Install pre-commit hooks and run this check when committing (uses the Conventional Precommit Linter).
⚠️	The source branch "fix_advertisedDevice_toString" incorrect format: contains uppercase letters. This can cause troubles on case-insensitive file systems (macOS). Please rename your branch.

👋 Hello Oros42, we appreciate your contribution to this project!

---

📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

---

🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project.

---

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 77e678e

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Test Results

 76 files   76 suites   17m 46s ⏱️
 38 tests  37 ✅ 0 💤 1 ❌
241 runs  240 ✅ 0 💤 1 ❌

For more details on these failures, see this check.

Results for commit 77e678e.

♻️ This comment has been updated with latest results.

[github-actions]

Memory usage test (comparing PR against master branch)

The table below shows the summary of memory usage change (decrease - increase) in bytes and percentage for each target.

Memory	FLASH [bytes]		FLASH [%]		RAM [bytes]		RAM [%]
Target	DEC	INC	DEC	INC	DEC	INC	DEC	INC
ESP32C5	0	0	0.00	0.00	0	0	0.00	0.00
ESP32P4	0	0	0.00	0.00	0	0	0.00	0.00
ESP32S3	0	0	0.00	0.00	0	0	0.00	0.00
ESP32C3	0	0	0.00	0.00	0	0	0.00	0.00
ESP32C6	0	0	0.00	0.00	0	0	0.00	0.00
ESP32H2	0	0	0.00	0.00	0	0	0.00	0.00
ESP32	0	0	0.00	0.00	0	0	0.00	0.00

Click to expand the detailed deltas report [usage change in BYTES]

Target	ESP32C5		ESP32P4		ESP32S3		ESP32C3		ESP32C6		ESP32H2		ESP32
Example	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM
libraries/BLE/examples/Beacon_Scanner	0	0	0	0	0	0	0	0	0	0	0	0	0	0
libraries/BLE/examples/Client	0	0	0	0	0	0	0	0	0	0	0	0	0	0
libraries/BLE/examples/Client_multiconnect	0	0	0	0	0	0	0	0	0	0	0	0	0	0
libraries/BLE/examples/Client_secure_static_passkey	0	0	0	0	0	0	0	0	0	0	0	0	0	0
libraries/BLE/examples/EddystoneTLM_Beacon	0	0	0	0	0	0	0	0	0	0	0	0	0	0
libraries/BLE/examples/EddystoneURL_Beacon	0	0	0	0	0	0	0	0	0	0	0	0	0	0
libraries/BLE/examples/Notify	0	0	0	0	0	0	0	0	0	0	0	0	0	0
libraries/BLE/examples/Scan	0	0	0	0	0	0	0	0	0	0	0	0	0	0
libraries/BLE/examples/Server	0	0	0	0	0	0	0	0	0	0	0	0	0	0
libraries/BLE/examples/Server_multiconnect	0	0	0	0	0	0	0	0	0	0	0	0	0	0
libraries/BLE/examples/Server_secure_authorization	0	0	-	-	0	0	0	0	0	0	0	0	-	-
libraries/BLE/examples/Server_secure_static_passkey	0	0	0	0	0	0	0	0	0	0	0	0	0	0
libraries/BLE/examples/UART	0	0	0	0	0	0	0	0	0	0	0	0	0	0
libraries/BLE/examples/Write	0	0	0	0	0	0	0	0	0	0	0	0	0	0
libraries/BLE/examples/iBeacon	0	0	0	0	0	0	0	0	0	0	0	0	0	0