Package colored_text for PyPI with typed API and CI

[Copilot]

The repo now ships a typed colored_text library (not just a notebook) with packaging, tests, CI, and publishing instructions for PyPI readiness.

• Packaging & Metadata: Added pyproject.toml/setup.cfg, MIT license, py.typed, pinned build backend, and README install/usage/publish guidance.
• Library Structure: Introduced src/colored_text with Style enum plus colorize/print_colored API and available styles helper.
• Quality & CI: Added pytest coverage for styling and invalid inputs; GitHub Actions workflow builds, tests, and runs twine check with restricted token permissions.

Example usage:

from colored_text import Style, available_styles, colorize, print_colored

print(colorize("Hello", Style.BOLD, Style.BLUE))
print_colored("Warn", "red", "underline")
print(available_styles())

Original prompt

Turn this repo into a fully packaged, installable Python library ready for publishing to PyPI. The repository currently has code for colored text printing in Python. I want:

1. A proper package directory (e.g., colored_text) with Python modules, not just a notebook.
2. A pyproject.toml configured for setuptools / build backend with metadata like name, version, author, description, license, classifiers, and homepage set correctly.
3. A minimal setup.cfg if needed to support editable installs and package discovery.
4. Include type hints and docstrings where applicable.
5. Write unit tests using pytest under a tests/ directory covering basic functionality (color application, invalid inputs, etc.).
6. Add GitHub Actions CI workflow (.github/workflows/python-package.yml) to build, test, and check packaging.
7. A README.md updated with installation instructions (pip install colored_text), usage examples, and contribution guidelines.
8. A LICENSE file with a permissive license (MIT by default) and update if needed.
9. Create a draft release and test publishing with twine check.
10. Ensure the package follows PyPI best practices (namespaced package, __init__.py, classifiers, Python version support).
11. Provide instructions in the PR description for how to publish to PyPI (build steps: python -m build, twine upload dist/*).

Write all new files and modifications as required, and open a pull request.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.