chore: bump minor rather than major for pre-1.0 breaking changes

Matches the sibling provider repos' release-please configuration. Without
this flag, release-please's default versioning escalates any breaking
change to a major bump even below 1.0.0 — the fix! in #64 retitled the
open release PR (#72) to 1.0.0 instead of 0.9.0. The 1.0 milestone
should be a deliberate decision, not a side effect of a config gap.

Author: tanderson-ld

release-please-config.json

@@ -3,6 +3,7 @@
     ".": {
       "release-type": "python",
       "versioning": "default",
+      "bump-minor-pre-major": true,
       "include-v-in-tag": false,
       "extra-files": ["docs/conf.py", "ld_openfeature/version.py"],
       "include-component-in-tag": false