fix: configure release-please for initial 0.2.0 release (#7)

Add release-please configuration and set versions to 0.1.0 to enable
the first release PR to bump to 0.2.0. This fixes the workflow failure
caused by missing release-please-config.json.

Changes:
- Add release-please-config.json with Python package configuration
- Set .release-please-manifest.json to 0.1.0 (from 0.2.0)
- Set pyproject.toml version to 0.1.0 (from 0.2.0)

This allows release-please to create a PR that will bump the version
to 0.2.0 for the first actual release.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: mldangelo

.release-please-manifest.json

@@ -1,3 +1,3 @@
 {
-  ".": "0.2.0"
+  ".": "0.1.0"
 }

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "promptfoo"
-version = "0.2.0"
+version = "0.1.0"
 description = "Python wrapper for the promptfoo CLI - LLM testing, red teaming, and security evaluation"
 authors = [
     { name = "Ian Webster", email = "ian@promptfoo.dev" },

release-please-config.json

@@ -0,0 +1,18 @@
+{
+  "packages": {
+    ".": {
+      "release-type": "python",
+      "package-name": "promptfoo",
+      "changelog-path": "CHANGELOG.md",
+      "bump-minor-pre-major": true,
+      "bump-patch-for-minor-pre-major": true,
+      "extra-files": [
+        {
+          "type": "generic",
+          "path": "pyproject.toml",
+          "glob": false
+        }
+      ]
+    }
+  }
+}