Add a new CodeCell ESP32C3 Board

[microbotsio]

Description

This pull request adds the CodeCell ESP32-C3 board to the Arduino-ESP32 package. The following changes are included:

• Added board configuration in boards.txt
• Included variant files specific to CodeCell

Changes Made

• boards.txt: Added configuration for CodeCell ESP32-C3.
• variants/CodeCell: Added pin mappings and variant configuration files.

Testing

Tested the board configuration by compiling and uploading sample sketches. Verified that the board appears in the Arduino IDE and uploads successfully.

Notes

• The default upload speed is set to 921600.
• USB CDC on boot is enabled by default.

[github-actions]

	Warnings
⚠️	Some issues found for the commit messages in this PR: the commit message "Add files via upload": summary looks empty type/action looks empty the commit message "Update boards.txt": summary looks empty type/action looks empty the commit message "Update boards.txt": summary looks empty type/action looks empty the commit message "Update boards.txt": summary looks empty type/action looks empty the commit message "Update boards.txt": summary looks empty type/action looks empty the commit message "Update boards.txt": summary looks empty type/action looks empty the commit message "Update variants/CodeCell/pins_arduino.h": summary looks empty type/action looks empty Please fix these commit messages - here are some basic tips: follow Conventional Commits style correct format of commit message should be: <type/action>(<scope/component>): <summary>, for example fix(esp32): Fixed startup timeout issue allowed types are: change,ci,docs,feat,fix,refactor,remove,revert,test sufficiently descriptive message summary should be between 20 to 72 characters and start with upper case letter avoid Jira references in commit messages (unavailable/irrelevant for our customers) TIP: Install pre-commit hooks and run this check when committing (uses the Conventional Precommit Linter).
⚠️	Please consider squashing your 7 commits (simplifying branch history).

👋 Hello microbotsio, we appreciate your contribution to 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.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- 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.

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 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.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 0223f72

[P-R-O-C-H-Y]

@microbotsio PTAL on my comments.
Also what I would recommend is to add the options to set different DebugLevel.

[P-R-O-C-H-Y]

@microbotsio Looks good :)
Please fix conflicts so we can merge :)