[FR][Ender 3 V2][BOUNTY $75AUD] - Add Marlin Z-Offset Wizard functionality to Ender 3 v2

[CRCinAU]

Aim

This bounty is to get an operational Z-Offset Wizard as provided in the Marlin bugfix-2.0.x codebase and make it usable on DWIN based screens.

This will require:

• Screen UI dialogs / input code
• Adding a Z-Offset Wizard menu to the existing 'Prepare' DWIN menu structure

The focus should be on the Ender 3 v2 DWIN implementation at:
https://github.com/MarlinFirmware/Marlin/tree/bugfix-2.0.x/Marlin/src/lcd/dwin/e3v2

Some code may benefit from being implemented in the main DWIN parts - and a focus on code reuse should be observed.

The base of this works will shall use code already merged via:
#20239

The workflow to follow for implementation in the DWIN display system shall emulate the flow already existing in non-DWIN displays.

Conditions

• All code be compliant with the Marlin Coding Standards published: https://marlinfw.org/docs/development/coding_standards.html
• In the event of multiple implementations, the solution accepted by the project maintainers will be considered successful.
• Successful claims will be made via PayPal to an address provided in the Accepted Pull Request.
• Any proposed code must be given freely to the project with no further claims.
• All proposed code must comply with any applicable licenses in the Marlin project.

Successful Claims

The bounty will be considered completed once all the following has occured:

• Functionality has been verified and confirmed
• A Pull Request has been submitted against the bugfix-2.0.x branch of Marlin
• Any modifications / issues raised by maintainers have been addressed
• The pull request has been merged into the bugfix-2.0.x branch

This bounty is operated by the Marlin Firmware Service (https://marlin.crc.id.au) and is not organised by the Marlin project. In the event of any dispute, the decision of Marlin Firmware Service shall be final.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.