Move encoder config to data driven based on #19923

[Trex4Git]

Move encoder config to data driven based on qmk#19923
Update config.h
Update info.json

Description

Types of Changes

• Core
• Bugfix
• New feature
• Enhancement/optimization
• Keyboard (addition or update)
• Keymap/layout/userspace (addition or update)
• Documentation

Issues Fixed or Closed by This PR

Checklist

• My code follows the code style of this project: C, Python
• I have read the PR Checklist document and have made the appropriate changes.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[BenRoe]

Where do you found information, about the split encoder stuff.
There is no information about that here and could not find it elsewhere. https://docs.qmk.fm/#/reference_info_json?id=encoders

[Trex4Git]

Seen the information at the QMK discord: https://discord.com/channels/440868230475677696/440868230475677698/1015546413033193542
And also a concrete implementation at the splitkb kyria re3 board: https://github.com/qmk/qmk_firmware/blob/master/keyboards/splitkb/kyria/rev3/info.json

[Trex4Git]

Also seen this in the big PR 19923 "Move encoder config to data driven"
https://github.com/qmk/qmk_firmware/pull/19923/files
e.g. for keyboards/aleblazer/zodiark/info.json

[github-actions]

Thank you for your contribution!
This pull request has been automatically marked as stale because it has not had activity in the last 45 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, or re-open when it's ready.
For maintainers: Please label with bug, awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.

[github-actions]

Thank you for your contribution!
This pull request has been automatically closed because it has not had activity in the last 30 days. Please feel free to give a status update now, ping for review, or re-open when it's ready.
// [stale-action-closed]