esp_lcd: Fix ST7789V display offset issue (IDFGH-14575)

[jomoly]

The ST7789V LCD shows a 20-pixel offset issue due to missing display window initialization. This commit adds proper CASET and RASET commands in panel initialization to fix the problem.

Fixes #15331

Description

Fixed ST7789V LCD display offset issue by adding proper display window initialization commands (CASET/RASET) in panel_st7789_init().

Issue

• Top 20 pixels show noise
• Content is shifted down by 20 pixels
• Bottom 20 pixels are cut off

Root Cause

Default initialization sequence lacks proper display window setup.

Solution

Added CASET and RASET commands to initialize display window properly:

• CASET: Set column address range (0-239)
• RASET: Set row address range (0-319)

Verification

Tested with:

• Hardware: ESP32-S3 with ST7789V LCD (240x320)
• Example: lcd_i80_display example
• Result: Display content shows correctly without offset

Documentation

No documentation changes needed as this is a bug fix.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

	Messages
📖	🎉 Good Job! All checks are passing!

👋 Hello jomoly, 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 via this public GitHub repository.

This GitHub project is public mirror of our internal git repository

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 synchronize it into our internal git repository.
4. In the internal git repository 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.
5. If the change is approved and passes the tests it is merged into the default branch.
5. On next sync from the internal git repository merged change will appear in this public GitHub repository.

Generated by 🚫 dangerJS against a96919f

[asaitov]

What if display resolution is not 240x320? I believe these changes are device specific and should not be part of ST7789 driver implementation.

[suda-morris]

CASET and RASET are also set in the panel_st7789_draw_bitmap. So maybe here is duplicated.