Update solver documentation - for v1.14

[jajhall]

This page will be correct when cuPDLP-C is replaced by HiPDLP, and the QP IPM solver is added, so this is just a draft PR

[jajhall]

Closes #2781

[codecov]

Codecov Report

❌ Patch coverage is 66.66667% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 80.33%. Comparing base (946a7bb) to head (f81fddc).
⚠️ Report is 20 commits behind head on latest.

Files with missing lines	Patch %	Lines
highs/lp_data/HighsOptions.h	66.66%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##           latest    #2787   +/-   ##
=======================================
  Coverage   80.33%   80.33%           
=======================================
  Files         348      348           
  Lines       86084    86084           
=======================================
  Hits        69152    69152           
  Misses      16932    16932           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jajhall]

Closes #2752

[filikat]

In definitions.md for option solver, should there be both "pdlp" and "hipdlp"? The option for "pdlp" should also coincide with what is used in the Summary of solvers.md.
It seems like you removed the statements "Setting the solver option to ... forces the ... solver to be used" from the LP section, since they are now present in the summary. But they still appear in the QP section. For consistency, it may be better to remove them from there as well.

[jajhall]

In definitions.md for option solver, should there be both "pdlp" and "hipdlp"? The option for "pdlp" should also coincide with what is used in the Summary of solvers.md.

Yes, the "hipdlp" value for solver is still in Yanyu's branch, so that she can run cuPDLPc (by setting "pdlp") for sanity checking, but it will disappear when we have only her PDLP solver

It seems like you removed the statements "Setting the solver option to ... forces the ... solver to be used" from the LP section, since they are now present in the summary. But they still appear in the QP section. For consistency, it may be better to remove them from there as well.

Indeed, I've updated solvers.md

[jajhall]

Documentation is fixed

[filikat]

@jajhall Maybe we should specify that options qp_iteration_limit, qp_nullspace_limit and qp_regularization_value refer to the active-set solver, to avoid confusion.