fix(SPIFFS): Use new disableWDT bool return value

[TD-er]

Analogue to this PR, but for SPIFFS: https://github.com/espressif/arduino-esp32/pull/10896/files

[github-actions]

Warnings

⚠️

Some issues found for the commit messages in this PR: the commit message "fix(SPIFFS): Use new disableWDT bool return value": scope/component should be lowercase without whitespace, allowed special characters are _ / . , * - . 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).

👋 Hello TD-er, 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 c77f69c

[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
ESP32P4	0	⚠️ +200	0.00	⚠️ +0.05	0	0	0.00	0.00
ESP32S3	0	⚠️ +160	0.00	⚠️ +0.04	0	0	0.00	0.00
ESP32S2	0	⚠️ +148	0.00	⚠️ +0.05	0	0	0.00	0.00
ESP32C3	0	⚠️ +172	0.00	⚠️ +0.05	0	0	0.00	0.00
ESP32C6	0	⚠️ +176	0.00	⚠️ +0.06	0	0	0.00	0.00
ESP32H2	0	⚠️ +172	0.00	⚠️ +0.05	0	0	0.00	0.00
ESP32	0	⚠️ +144	0.00	⚠️ +0.04	0	0	0.00	0.00

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

Target	ESP32P4		ESP32S3		ESP32S2		ESP32C3		ESP32C6		ESP32H2		ESP32
Example	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM
SPIFFS/examples/SPIFFS_Test	⚠️ +192	0	⚠️ +148	0	⚠️ +144	0	⚠️ +172	0	⚠️ +176	0	⚠️ +172	0	⚠️ +140	0
SPIFFS/examples/SPIFFS_time	⚠️ +200	0	⚠️ +160	0	⚠️ +148	0	⚠️ +172	0	⚠️ +172	0	-	-	⚠️ +144	0

[github-actions]

Test Results

 62 files   62 suites   5m 39s ⏱️
 21 tests  21 ✅ 0 💤 0 ❌
154 runs  154 ✅ 0 💤 0 ❌

Results for commit c77f69c.

♻️ This comment has been updated with latest results.