Ship 1.0.0: tag-driven PyPI publishing, and declare typing_extensions

[pip-install-python]

Publishing was a manual upload from a laptop; 0.1.0 went out that way and 0.1.1 never reached PyPI at all. Pushing a v* tag now does the whole thing: verify, run the same CI matrix cd.yml runs before a deploy, build, gate the artifacts, publish via OIDC trusted publishing (no stored token), and open a GitHub Release with notes lifted from CHANGELOG.md.

The gates are the point. A release refuses to proceed when the tag disagrees with package.json, when the tagged commit is not an ancestor of origin/main, or when CHANGELOG.md has no section for the version — and both the wheel and the sdist must carry the component bundle, since a package that installs cleanly and then renders nothing is otherwise indistinguishable from a good one. That last check runs from outside the checkout on purpose: a script fed to python on stdin puts the cwd at sys.path[0], and the repo root holds dash_mui_scheduler/ — run from there it imports the source tree and passes against a wheel that shipped nothing.

Also declares typing_extensions. Every generated wrapper imports it, and the package had been inheriting it from Dash; the floor is dash 2.11, which gated it behind a python_version marker, so an old-Dash resolution could install successfully and fail on import.

1.0.0 graduates the package out of 0.x — the component API has not changed since 0.1.0 and existing code keeps working untouched.