Add support for Chaz

[jasonhazel]

Description

Adding support for Chaz.

Had a previous PR for this board (#21091) but after seeing #21186 I closed it rework for RP2040 configurator support.

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

[jasonhazel]

I saw some comments come through relating to info.json information duplicated across files. I went to reply and they're missing now so I assume a single, all encompassing comment is coming?

There is a lot of overlap between the two version info.json. Is it safe to assume all of that overlap can be moved to the top level info.json?

[dunk2k]

@jasonhazel

There is a lot of overlap between the two version info.json. Is it safe to assume all of that overlap can be moved to the top level info.json?

you got it chief! There's argument for moving/merging the readme.md's to keyboard level, but I'll let the collaborators call that one 😉

[jasonhazel]

@dunk2k right on. I applied your suggestions and will wait to see what the collaborators say about the readme. Thanks for your feedback!

[drashna]

It's using the same pinout as the pro micro, correct?

[jasonhazel]

@drashna I realized converters could be specified via rules.mk. I've rearranged things to a single top-level info.json with promicro pins specified and then a sub directory for rp2040ce with the converter defined in the rules.mk.

[fauxpark]

Converters at keyboard level won't work with Configurator.