Fix version qualifiers in pyproject.toml files

[obulat]

Fixes

Related to #4166 by @dhruvkb

Description

@dhruvkb has flagged the fact that the PRs migrating to PDM were setting versions incorrectly, not in the way we use in the API.
This PR updates the version qualifiers:
>=x.y -> >=x.y.z, <x+1.
This prevents PDM from updating the version to the next major version.

Testing Instructions

CI should pass.

Checklist

• My pull request has a descriptive title (not a vague title likeUpdate index.md).
• My pull request targets the default branch of the repository (main) or a parent feature branch.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added or updated tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no visible errors.
• I ran the DAG documentation generator (ov just catalog/generate-docs for catalog
  PRs) or the media properties generator (ov just catalog/generate-docs media-props
  for the catalog or ov just api/generate-docs for the API) where applicable.

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[dhruvkb]

Thanks for accommodating these changes!

It seems like the content hash was updated for utilities/dead_links, but didn't for the other 2 utilities projects?

[obulat]

It seems like the content hash was updated for utilities/dead_links, but didn't for the other 2 utilities projects?

I'm not sure why that happened.
I re-ran pdm install but it didn't update the lock file. There was a warning WARNING: Lockfile is generated on an older version of PDM, so I deleted the lock file and re-ran pdm install, and the lock file updated the hash, groups and some other dependencies.

Do you know if the lock files are not updated when different pdm versions are used, @dhruvkb ?

[dhruvkb]

Sorry, I don't know what happens if PDM encounters a lockfile generated by an older version of itself.