[ceres] update to 2.2.0

[Cheney-W]

Fixes #34483

According to ceres-solver/ceres-solver@2335b5b, remove feature cxsparse.
According to ceres-solver/ceres-solver@0c88301, add dependency metis for feature eigensparse.
Modify 0003_fix_exported_ceres_config.patch to add the required dependencies.
Modify find-package-required.patch to use the ports provided by vcpkg.

• Changes comply with the maintainer guide
• SHA512s are updated for each updated download
• The "supports" clause reflects platforms that may be fixed by this new version
• Any fixed CI baseline entries are removed from that file.
• Any patches that are no longer applied are deleted from the port's directory.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is added to each modified port's versions file.

[Cheney-W]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[dg0yt]

Make good use of find_package(... NAMES ...) and add_library(... ALIAS ...) to trim the patch size.

[patrikhuber]

According to ceres-solver/ceres-solver@0c88301, add dependency metis for feature eigensparse.

If I understood you correctly, you want to add a dependency on metis whenever the feature ceres[eigensparse] is requested? As far as I understand ceres-solver/ceres-solver@0c88301, metis is not a dependency of eigensparse, it's an optional extra (depending on CERES_NO_EIGEN_METIS). If that is the case, then please don't pull in metis as a dependency whenever someone requests ceres[eigensparse] - only pull in metis as a dependency if someone actually requests ceres[metis]. There is a big appeal in having a minimal (almost-)no dependency ceres when one does vcpkg install ceres[eigensparse].

[hesmar]

What is the status of this PR? Is anyone still working on it? I would like to create another patch for Ceres which will be based on 2.2.0. So it would be nice to have this in master.

[patrikhuber]

It would be really great to have Ceres 2.2.0 available in vcpkg, it's been out for quite a few months now.

[hesmar]

@Cheney-W Are you still working on it?

[moolawooda]

So, is there any progress at the moment?

[saulthu]

Bump🤜

[saulthu]

@Cheney-W Any update on why this was closed? (Thanks for the efforts BTW!)

[valgur]

Just FYI, I intend to re-open a v2.2.0 PR after #39297 is merged.

[Cheney-W]

I encountered some compilation issues during the update, and I'm not sure how to resolve them yet. To avoid blocking others from updating this port, I've decided to close this PR for now. I will carefully investigate the errors on my local machine, and once I resolve them, if no one else has updated this port, I will reopen my PR.