fix(ble): Fix default advertising name in NimBLE

[lucasssvaz]

Description of Change

This pull request improves how the BLE device name is managed and advertised by ensuring consistent storage and retrieval across the BLE stack. The main focus is on reliably setting and using the device name for BLE advertising, addressing issues where the underlying GAP service did not always reflect the intended name.

Device Name Management Improvements:

• Added a static member m_deviceName to BLEDevice to store the device name persistently, and provided a static getDeviceName() method for access (BLEDevice.cpp, BLEDevice.h). [1] [2] [3] [4]
• Changed the initialization logic to store the device name in m_deviceName during BLEDevice::init instead of immediately setting it on the GAP service, deferring the actual GAP update until BLE stack synchronization (BLEDevice.cpp).
• Updated BLEDevice::onSync to set the device name on the GAP service from m_deviceName after stack synchronization, improving reliability and ensuring the device name is always correctly set (BLEDevice.cpp).

Advertising Logic Enhancements:

• Modified BLEAdvertising::start to retrieve the device name directly from BLEDevice::getDeviceName() if not already set, and ensure it is included in the advertising data, working around issues with the GAP service name getter (BLEAdvertising.cpp).

Test Scenarios

Tested locally

[github-actions]

	Messages
📖	🎉 Good Job! All checks are passing!

👋 Hello lucasssvaz, 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.
- 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 c704a6a

[github-actions]

Test Results

 90 files   90 suites   32m 15s ⏱️
 67 tests  67 ✅ 0 💤 0 ❌
683 runs  683 ✅ 0 💤 0 ❌

Results for commit c704a6a.

[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
ESP32	0	0	0.00	0.00	0	0	0.00	0.00
ESP32C3	0	⚠️ +338	0.00	⚠️ +0.05	0	⚠️ +16	0.00	⚠️ +0.10
ESP32C5	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	⚠️ +340	0.00	⚠️ +0.05	0	⚠️ +16	0.00	⚠️ +0.10
ESP32P4	0	⚠️ +334	0.00	⚠️ +0.04	0	⚠️ +16	0.00	⚠️ +0.06
ESP32S3	0	⚠️ +344	0.00	⚠️ +0.05	0	⚠️ +16	0.00	⚠️ +0.06

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

Target	ESP32		ESP32C3		ESP32C5		ESP32C6		ESP32H2		ESP32P4		ESP32S3
Example	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM
libraries/BLE/examples/Beacon_Scanner	0	0	⚠️ +338	⚠️ +16	-	-	-	-	⚠️ +328	⚠️ +16	⚠️ +328	⚠️ +16	⚠️ +336	⚠️ +16
libraries/BLE/examples/Client	0	0	⚠️ +334	⚠️ +16	-	-	-	-	⚠️ +326	⚠️ +16	⚠️ +326	⚠️ +16	⚠️ +344	⚠️ +16
libraries/BLE/examples/Client_Server	0	0	⚠️ +326	⚠️ +16	-	-	-	-	⚠️ +326	⚠️ +16	⚠️ +326	⚠️ +16	-	-
libraries/BLE/examples/Client_multiconnect	0	0	⚠️ +334	⚠️ +16	-	-	-	-	⚠️ +332	⚠️ +16	⚠️ +324	⚠️ +16	-	-
libraries/BLE/examples/Client_secure_static_passkey	0	0	⚠️ +324	⚠️ +16	-	-	-	-	⚠️ +324	⚠️ +16	⚠️ +324	⚠️ +16	-	-
libraries/BLE/examples/EddystoneTLM_Beacon	0	0	⚠️ +330	⚠️ +16	-	-	-	-	⚠️ +336	⚠️ +16	⚠️ +330	⚠️ +16	-	-
libraries/BLE/examples/EddystoneURL_Beacon	0	0	⚠️ +336	⚠️ +16	-	-	-	-	⚠️ +328	⚠️ +16	⚠️ +330	⚠️ +16	-	-
libraries/BLE/examples/Notify	0	0	⚠️ +330	⚠️ +16	-	-	-	-	⚠️ +338	⚠️ +16	⚠️ +330	⚠️ +16	-	-
libraries/BLE/examples/Scan	0	0	⚠️ +332	⚠️ +16	-	-	-	-	⚠️ +340	⚠️ +16	⚠️ +330	⚠️ +16	-	-
libraries/BLE/examples/Server	0	0	⚠️ +330	⚠️ +16	-	-	-	-	⚠️ +336	⚠️ +16	⚠️ +328	⚠️ +16	-	-
libraries/BLE/examples/Server_multiconnect	0	0	⚠️ +336	⚠️ +16	-	-	-	-	⚠️ +328	⚠️ +16	⚠️ +328	⚠️ +16	-	-
libraries/BLE/examples/Server_secure_static_passkey	0	0	⚠️ +332	⚠️ +16	-	-	-	-	⚠️ +334	⚠️ +16	⚠️ +334	⚠️ +16	-	-
libraries/BLE/examples/UART	0	0	⚠️ +338	⚠️ +16	-	-	-	-	⚠️ +328	⚠️ +16	⚠️ +328	⚠️ +16	-	-
libraries/BLE/examples/Write	0	0	⚠️ +336	⚠️ +16	-	-	-	-	⚠️ +330	⚠️ +16	⚠️ +330	⚠️ +16	-	-
libraries/BLE/examples/iBeacon	0	0	⚠️ +336	⚠️ +16	-	-	-	-	⚠️ +326	⚠️ +16	⚠️ +326	⚠️ +16	-	-
libraries/BLE/examples/Server_secure_authorization	-	-	⚠️ +338	⚠️ +16	-	-	-	-	⚠️ +336	⚠️ +16	-	-	-	-