Migrate from obsolete setup.py to modern pyproject.toml packaging and remove obsolete CI/CD files

[Copilot]

This PR modernizes the Python packaging configuration by migrating from the obsolete setup.py to the modern pyproject.toml format as recommended by PEP 621, and removes obsolete CI/CD configuration files.

Changes Made

• Added pyproject.toml with PEP 621 compliant configuration
• Removed obsolete setup.py file
• Removed obsolete azure-pipelines.yml file
• Preserved all existing metadata including package name, version, author, license, and classifiers
• Maintained backward compatibility - no functional changes to the package

Benefits

• Modern standard: Adopts the recommended approach for Python packaging
• Better tooling support: Improved compatibility with modern Python build tools
• Cleaner configuration: More readable and maintainable package metadata
• Reduced maintenance burden: Removes outdated CI/CD configuration
• Future-proof: Aligns with current Python packaging best practices

Verification

The migration was thoroughly tested to ensure:

• ✅ Package installs correctly with pip install -e .
• ✅ All functionality remains unchanged (imports, object creation work)
• ✅ Wheel building succeeds with python -m build
• ✅ Built wheels install and function correctly
• ✅ All metadata is preserved (name, version, author, classifiers, etc.)

The pyproject.toml configuration maintains the exact same package metadata as the original setup.py, ensuring no breaking changes for users.

Fixes #8.

---

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

[paulbkoch]

@copilot -- can you also remove the obsolete azure-pipelines.yml file

[Copilot]

@copilot -- can you also remove the obsolete azure-pipelines.yml file

Done! Removed the obsolete azure-pipelines.yml file in commit a383e2d.