Prep for v1.23.0

[odow]

Pre-release

• [x] Check that the pinned packages in docs/Project.toml are updated. We pin the versions so that changes in the solvers (changes in printing, small numeric changes) do not break the printing of the JuMP docs in arbitrary commits.
• [x] Check that the rev fields in docs/packages.toml are updated. We pin the versions of solvers and extensions to ensure that changes to their READMEs do not break the JuMP docs in arbitrary commits, and to ensure that the versions are compatible with the latest JuMP and MathOptInterface releases.
• [x] Check compat of DimensionalData in Project.toml
• [x] Check compat of MacroTools in Project.toml
• [x] Update docs/src/changelog.md
• [x] https://github.com/jump-dev/JuMP.jl/actions/runs/10261874110
• [x] https://github.com/jump-dev/JuMP.jl/actions/runs/10360429801 Lots of breakage
  • [x] Alpine
  • [x] BilevelJuMP
  • [x] InfiniteOpt https://github.com/infiniteopt/InfiniteOpt.jl/pull/361
  • [x] LinearFractional: issue is on their end https://github.com/nexteraanalytics/LinearFractional.jl/pull/21#discussion_r1705026288. Will be fixed by https://github.com/nexteraanalytics/LinearFractional.jl/pull/22
  • [x] PolyJuMP: @blegat?
  • [x] SDDP: should be fixed by https://github.com/odow/SDDP.jl/pull/770
  • [x] SumOfSquares: @blegat?
• [x] Change the version number in Project.toml
• [x] The commit messages in this PR do not contain [ci skip]

The release

• [x] After merging this pull request, comment [at]JuliaRegistrator register in the GitHub commit. This should automatically publish a new version to the Julia registry, as well as create a tag, and rebuild the documentation for this tag.

  These steps can take quite a bit of time (1 hour or more), so don't be surprised if the new documentation takes a while to appear. In addition, the links in the README will be broken until JuliaHub fetches the new version on their servers.

Post-release

• [x] Once the tag is created, update the relevant release- branch. The latest release branch at the time of writing is release-1.0 (we haven't back-ported any patches that needed to create a release-1.Y branch). To to update the release branch with the v1.10.0 tag, do:

     git checkout release-1.0
     git pull
     git merge v1.10.0
     git push

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 97.90%. Comparing base (34ec0a0) to head (24149ad).

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #3799 +/- ## ======================================= Coverage 97.90% 97.90% ======================================= Files 44 44 Lines 6020 6020 ======================================= Hits 5894 5894 Misses 126 126 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[blegat]

PolyJuMP and SumOfSquares failing can be ignore, they need to checkout a few packages for the tests to work

[odow]

@joaquimg BilevelJuMP is:

[odow]

Okay, I think this is ready