chore: Bump fgpyo to ^1.0.0

[msto]

We have a client repository depending on the dev branch of prymer, and this pin is causing some dependency conflicts.

The pinned commit is on the main branch of fgpyo, so I think it's safe to move to a version pin instead.

[msto]

Tests are currently failing because local poetry locked to numpy=2.2.3, which came out half an hour ago, and GHA poetry can't find the new version yet.

And, afaict, there's no way to give poetry a constraint at the command line (e.g. to create a lockfile with numpy at 2.22.2).

python-poetry/poetry#2758

We just have to wait for the cache to refresh 😞

[msto]

For posterity, this thread helped me resolve the issue:

python-poetry/poetry#8139

These failures may occur when the local lock file was created before PyPI completed generating all the wheels for a package version. Waiting a bit and then re-generating the lock file was sufficient to resolve.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.96%. Comparing base (b86dbcd) to head (161fc7e).
Report is 1 commits behind head on dev.

Additional details and impacted files

@@           Coverage Diff           @@
##              dev     #125   +/-   ##
=======================================
  Coverage   94.96%   94.96%           
=======================================
  Files          16       16           
  Lines        1411     1411           
  Branches      161      161           
=======================================
  Hits         1340     1340           
  Misses         49       49           
  Partials       22       22           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.