Move theming support from Beta to Main

[jordanjones243]

Alaska Airlines Pull Request

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Resolves: #124

Summary:

Please summarize the scope of the changes you have submitted, what the intent of the work is and anything that describes the before/after state of the project.

Type of change:

Please delete options that are not relevant.

• [x] New capability
• [x] Revision of an existing capability
• [ ] Infrastructure change (automation, etc.)
• [ ] Other (please elaborate)

Checklist:

• [x] My update follows the CONTRIBUTING guidelines of this project
• [x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.

Thank you for your submission!
-- Auro Design System Team

Summary by Sourcery

Move theming support from Beta to Main by introducing theme support for the auro-radio component, allowing customization through design tokens. Refactor styles into separate SCSS files for improved modularity and update documentation to guide users on utilizing the new theming capabilities.

New Features:

• Introduce theme support for the auro-radio component, allowing customization of styles using design tokens.

Enhancements:

• Refactor the styling approach by separating color and token styles into new SCSS files for better modularity and maintainability.

Documentation:

• Update documentation to include information on how to restyle components using the new theme support.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

:white_check_mark: jason-capsule42
:x: semantic-release-bot
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[sourcery-ai[bot]]

Reviewer's Guide by Sourcery

This pull request moves theming support from Beta to Main for the auro-radio component. The changes primarily involve updating the styling approach to use CSS custom properties for theming, removing hardcoded color values, and introducing new SCSS files for color and token management. The implementation focuses on improving the component's flexibility and customization options while maintaining its core functionality.

File-Level Changes

Files	Changes
src/style.scss	Removed hardcoded color values and shadow styles from the main SCSS file
demo/api.md	Added theme support documentation in the API markdown file
src/auro-radio.js	Updated event documentation in the component class
src/auro-radio-group.scss	Removed specific color styles from the radio group SCSS file
CHANGELOG.md	Updated CHANGELOG.md with new version and features
src/auro-radio-group.js	Updated styles import in the radio group component
docs/partials/api.md	Added theme support section in the API documentation
README.md	Updated CDN link in README.md to the new version
src/color.scss	Added new color.scss file for managing color-related styles
src/groupColor.scss	Added new groupColor.scss file for radio group color management
src/tokens.scss	Added new tokens.scss file for defining CSS custom properties

---

Tips

- Trigger a new Sourcery review by commenting `@sourcery-ai review` on the pull request. - Continue your discussion with Sourcery by replying directly to review comments. - You can change your review settings at any time by accessing your [dashboard](https://app.sourcery.ai): - Enable or disable the Sourcery-generated pull request summary or reviewer's guide; - Change the review language; - You can always [contact us](mailto:support@sourcery.ai) if you have any questions or feedback.