phase4-D: bump to v0.1.0 + add make build

[rafael5]

Summary

Phase 4 Track D §5 D1 — release-prep PR. The v0.1.0 tag + gh release create happen on main once this lands.

What changed

• pyproject.toml version 0.0.1 → 0.1.0
• __version__ in src/m_dev_tools_mcp/__init__.py → 0.1.0
• New build>=1.2 dev-extra so contributors can make build without a separate uv install
• New make build target — PEP-517 python -m build --wheel → dist/m_dev_tools_mcp-0.1.0-py3-none-any.whl. Pure-Python; no compiled extensions, no platform pin
• make clean extended to drop dist/*.whl / dist/*.tar.gz (the manifest + repo.meta.json under dist/ stay tracked; only the build outputs are blown away)
• dist/mcp-tools.json regenerated — the version field embeds the package version so the drift gate catches stale bumps

Verified locally

• make check green (41/41 pytest, ruff + mypy clean, manifest + agents drift gates clean)
• make build produces dist/m_dev_tools_mcp-0.1.0-py3-none-any.whl
• Fresh-venv install: pip install dist/m_dev_tools_mcp-0.1.0-py3-none-any.whl in a mktemp -d venv exposes m-dev-tools-mcp --version printing 0.1.0

What's NOT in this PR

• The v0.1.0 git tag and the GitHub Release with the wheel attached — those land on main after this merges (Track D §5 D2).
• The catalog onboarding (tool:m-dev-tools-mcp entry in .github/profile/tools.json with release_wheel_url) — that's a follow-up PR on the .github repo (Track D §5 D3–D5).

Test plan

• make check green
• make build produces the wheel
• Wheel installs into a fresh venv and --version prints 0.1.0
• CI green