Fix/flash erase area

[erhankur]

• When adding a public flash API, it must support large flash mode. stub_lib_flash_erase_sector and stub_lib_flash_erase_block did not support large mode, so I removed them.
• stub_lib_flash_erase_area is now implemented using functions that support large flash mode.
• And removed some unnecessary log prints and reduced log levels as verbose

[github-actions]

	Messages
📖	You might consider squashing your 4 commits (simplifying branch history).

👋 Hello erhankur, we appreciate your contribution to 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.
- Addressing info messages (📖) is strongly recommended; they're less critical but valuable.
- 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 50c8f44

[Copilot]

Pull request overview

This pull request refactors the flash erase API to ensure all public functions support large flash mode (>16MB) using 4-byte addressing. The PR removes stub_lib_flash_erase_sector and stub_lib_flash_erase_block from the public API because they didn't support large flash mode, and reimplements stub_lib_flash_erase_area to use the existing stub_lib_flash_start_next_erase helper which properly handles both regular and large flash modes. Additionally, the PR reduces logging verbosity by converting TRACE-level logs to VERBOSE-level and removing some redundant log statements.

Changes:

• Removed stub_lib_flash_erase_sector and stub_lib_flash_erase_block from public and internal APIs
• Reimplemented stub_lib_flash_erase_area to support large flash mode using stub_lib_flash_start_next_erase
• Reduced log verbosity across all target implementations by converting STUB_LOG_TRACEF to STUB_LOGV and removing redundant logs

Reviewed changes

Copilot reviewed 18 out of 18 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
include/esp-stub-lib/flash.h	Removed public API declarations for stub_lib_flash_erase_sector and stub_lib_flash_erase_block
src/flash.c	Reimplemented stub_lib_flash_erase_area with large flash support, reduced log verbosity, removed old erase functions, increased severity of unknown flash ID warning
src/target/base/include/target/flash.h	Removed internal API declarations for sector/block/area erase functions
src/target/common/src/flash.c	Removed common implementations of sector/block/area erase functions and redundant trace logs
src/target/esp8266/src/flash.c	Converted STUB_LOG_TRACEF to STUB_LOGV for erase operations, removed redundant write result log
src/target/esp32/src/flash.c	Converted STUB_LOG_TRACEF to STUB_LOGV for erase operations
src/target/esp32s2/src/flash.c	Converted STUB_LOG_TRACEF to STUB_LOGV for erase operations
src/target/esp32s3/src/flash.c	Converted STUB_LOG_TRACEF to STUB_LOGV for erase operations, increased octal mode log from debug to info
src/target/esp32c2/src/flash.c	Converted STUB_LOG_TRACEF to STUB_LOGV for erase operations
src/target/esp32c3/src/flash.c	Converted STUB_LOG_TRACEF to STUB_LOGV for erase operations
src/target/esp32c5/src/flash.c	Converted STUB_LOG_TRACEF to STUB_LOGV for erase operations
src/target/esp32c6/src/flash.c	Converted STUB_LOG_TRACEF to STUB_LOGV for erase operations
src/target/esp32c61/src/flash.c	Converted STUB_LOG_TRACEF to STUB_LOGV for erase operations
src/target/esp32h2/src/flash.c	Converted STUB_LOG_TRACEF to STUB_LOGV for erase operations
src/target/esp32h4/src/flash.c	Converted STUB_LOG_TRACEF to STUB_LOGV for erase operations
src/target/esp32h21/src/flash.c	Converted STUB_LOG_TRACEF to STUB_LOGV for erase operations
src/target/esp32p4/src/flash.c	Converted STUB_LOG_TRACEF to STUB_LOGV for erase operations
example/stub_main.c	Updated example to remove usage of deprecated erase_sector and erase_block functions

[Dzarda7]

LGTM, thanks, nice update.

[Dzarda7]

Feel free to merge this, esp8266 issue is in recently merged commits.