fix(i2s): Use separate variables when reading and writing

[me-no-dev]

When reading and writing we should use separate variables for what we are sending/receiving and what has actually been sent/received. Failing to do so may cause wrong data on the output

[github-actions]

	Warnings
⚠️	The **target branch** for this Pull Request **must be the default branch** of the project (`master`). If you would like to add this feature to a different branch, please state this in the PR description and we will consider it.

👋 Hello me-no-dev, 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.
- 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 47b7c60

[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	0	0.00	0.00	0	0	0.00	0.00
ESP32S3	0	‼️ +22K	0.00	‼️ +6.48	0	⚠️ +1788	0.00	‼️ +9.41
ESP32S2	0	‼️ +15K	0.00	‼️ +5.42	0	⚠️ +1476	0.00	‼️ +10.36
ESP32C3	0	‼️ +14K	0.00	‼️ +4.33	0	⚠️ +1604	0.00	‼️ +13.00
ESP32C6	0	‼️ +15K	0.00	‼️ +5.76	0	⚠️ +1652	0.00	‼️ +12.48
ESP32H2	0	‼️ +12K	0.00	‼️ +3.75	0	⚠️ +1580	0.00	‼️ +11.66
ESP32	0	‼️ +18K	0.00	‼️ +5.44	0	⚠️ +728	0.00	‼️ +3.48

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
ESP_I2S/examples/ES8388_loopback	-	-	‼️ +21K	⚠️ +1788	‼️ +15K	⚠️ +1476	‼️ +14K	⚠️ +1604	‼️ +15K	⚠️ +1652	‼️ +12K	⚠️ +1580	‼️ +16K	⚠️ +704
ESP_I2S/examples/Record_to_WAV	-	-	‼️ +22K	⚠️ +1672	-	-	-	-	-	-	-	-	‼️ +18K	⚠️ +728
ESP_I2S/examples/Simple_tone	-	-	‼️ +19K	⚠️ +1648	‼️ +14K	⚠️ +1424	‼️ +11K	⚠️ +864	‼️ +13K	⚠️ +888	‼️ +10K	⚠️ +816	‼️ +16K	⚠️ +712

[github-actions]

Test Results

 62 files   62 suites   15m 41s ⏱️
 24 tests  18 ✅ 0 💤 6 ❌
140 runs  134 ✅ 0 💤 6 ❌

For more details on these failures, see this check.

Results for commit 47b7c60.

♻️ This comment has been updated with latest results.