Allow encoder config from info.json

[zvecr]

Description

Current plan is to munge https://docs.qmk.fm/#/feature_encoders into,

    "encoder": {
        "enabled": true,
        "rotary": [
            { "pin_a": "B5", "pin_b": "A2", "resolution": 2 }
        ]
    }

Once format has been decided, DD docs will be updated.

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).

[KarlK90]

How much work would it be to support ENCODER_DIRECTION_FLIP and ENCODER_DEFAULT_POS in this PR? Because that would cover all the encoder features besides callbacks and encoder maps.

Once format has been decided, DD docs will be updated.

As the format seems pretty much nailed down this can be added now?

Otherwise LGTM!

[zvecr]

ENCODER_DIRECTION_FLIP shouldnt exist at the keyboard level so wont have a ton of value (people should just swap a/b pins). ENCODER_DEFAULT_POS was only in 2 keymaps, though it could be added? Wasnt sure of its use case really to know how it factors in.

[drashna]

ENCODER_DEFAULT_POS is very much like the flip. I think it should only be set in keymap config.

[jvbroek]

Necro-ing here a tiny bit, I saw that the docs for encoders don't mention anything about info.json. Figured I'd draw attention to it.