docs(CHANGES) reframe libvcs 0.41 bump as Breaking changes

why: PR #544 (v1.59.0) established the convention that libvcs
version-coupling bumps land under `### Breaking changes`. This
PR's libvcs>=0.41.0 bump was filed under `### Development`, mixing
the version bump (breaking for downstream packagers) with the
test-side parameter renames (non-breaking, internal). Splitting
the entry restores parity with #544.
what:
- Move the libvcs version bump into a new `### Breaking changes`
  section, matching the v1.59.0 entry style (one terse bullet)
- Keep the test-side parameter renames and the [tool.uv.sources]
  note under `### Development`
- No content removed; only reorganised + headings added

Author: tony

CHANGES

@@ -37,16 +37,20 @@ $ uvx --from 'vcspull' --prerelease allow vcspull
 _Notes on upcoming releases will be added here_
 <!-- END PLACEHOLDER - ADD NEW CHANGELOG ENTRIES BELOW THIS LINE -->
 
-### Development
+### Breaking changes
 
-- Track libvcs's `vcs_gitconfig` fixture rename
+- Bump minimum libvcs from 0.40.0 to 0.41.0 to pick up the upstream
+  `vcs_gitconfig` / `vcs_hgconfig` pytest fixture rename
   ([libvcs#528](https://github.com/vcs-python/libvcs/issues/528),
-  [libvcs#529](https://github.com/vcs-python/libvcs/pull/529)). The
-  internal `setup()` autouse fixture in `conftest.py` and the
+  [libvcs#529](https://github.com/vcs-python/libvcs/pull/529))
+
+### Development
+
+- Internal `setup()` autouse fixture in `conftest.py` and the
   `test_home_contains_gitconfig` / `test_pytester_git_commit_in_isolated_run`
-  tests now request the renamed `vcs_gitconfig` parameter. Pinned to
-  `libvcs>=0.41.0,<0.42.0`; `[tool.uv.sources]` temporarily tracks the
-  libvcs branch until 0.41.0 ships.
+  tests now request the renamed `vcs_gitconfig` parameter.
+  `[tool.uv.sources]` temporarily tracks the libvcs branch until
+  0.41.0 ships on PyPI; drop in a follow-up PR after release.
 
 ### Documentation