First release pinned to 0.1.0

This configuration change sets the project's versioning strategy for its initial release. The release-please-config.json file now specifies that the first release should be 0.1.0 rather than the default 1.0.0. Combined with an existing bump-minor-pre-major setting, any future feature commits will increment the minor version within the 0.x range (0.1.0 → 0.2.0, and so on). The project can promote to a stable 1.0.0 release later by introducing a breaking change commit. This approach gives the team flexibility to stabilize the API before committing to major version semantics.