Documentation update for NEWPATHWAYS

[yiyi1991]

Update documentation for NEWPATHWAYS (a project starting from Jan 2025)

How to review

• The newpathways.rst contains all IIASA-related working packages, makes sense to internal modelers, and assigns the correct PL/PM.

PR checklist

• Add or expand tests; coverage checks both ✅
• Add, expand, or update documentation.
• Update doc/whatsnew.

p.s., once merged, Jun will be able to further work on the documentation of T3.5.
Aiming at updating the documentation when the next milestone is achieved (e.g., branches and workflows built for T3.3 or T3.5).

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.4%. Comparing base (dbd9030) to head (ef6f910).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##            main    #385     +/-   ##
=======================================
- Coverage   77.1%   76.4%   -0.8%     
=======================================
  Files        250     250             
  Lines      20198   20198             
=======================================
- Hits       15589   15433    -156     
- Misses      4609    4765    +156     

see 8 files with indirect coverage changes

🚀 New features to boost your workflow:

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

[junukitashepard]

Thanks for updating the documentation. I will add the trade portion.

[glatterf42]

Thanks for the PR and the review :)
Please help me understand how we can merge this: first of, we'll need to update this branch by rebasing it on the main branch (and force-pushing it). Do you feel comfortable doing so or should I help out?
Next, please let me know what else is required: can we tick the box in the "How to review" section in the PR description?
For the last remaining box, please take a look at the doc/whatsnew.rst file. This PR should be added there with one line similar to the others (in the section for the next release).
Lastly, are we fine with merging the PR without reviews from @amastrucci and @r-aneeque or should we wait for them? If we wait and you want to update this documentation, you can either use this branch or create a new branch on top of this one -- merging this one will then shift the new branch so that it starts from main automatically.

[yiyi1991]

Thanks Fridolin! Rebased. (And I think we can tick the box unless Jun or anyone else sees any simple typos or obvious mistakes.) Paul helped update the whatsnew last time (New summary pages for projects :doc:project/geidco, (:pull:312)), and I am happy to follow that style. Which section should I use? v2025.8.7?

And it is ok to merge with one reviewer confirmed. I actually filled documentation for quite a few projects (in branches doc/geidco, doc/newpathways, doc/elevate, doc/efc)... and will open PRs similar to this. It will be great if @khaeru can take a look too.

[glatterf42]

Happy to hear that more docs updates are coming soon :)
The section v2025.8.7 should not be used for writing new items anymore; this release has already been published, so we can't add anything to it. In this case, you should modify these lines by removing the .. in the beginning (including the whitespace) and then collect your items there :)

From my point of view, if you tell me that the information you added here is good, we can merge with a single approval. But if you think someone should take another look in particular, we can also wait until that person has time (and maybe tell them in person about this PR, including that it only takes x minutes to review).

[khaeru]

Please go ahead and merge. I think it will be much easier to tidy, edit, standardize in batches, once we can see what kinds of info are contained in the documentation for multiple projects.

It's also simple to fill gaps if anyone later realizes some info was missing from this PR. No need to delay.

[yiyi1991]

Thanks both. I added the whatsnew of it and similar updates of EFC and ELEVATE documentations will come soon too. Kindly help with any tidy/edit/standardize/etc. then.

[glatterf42]

(Merging this without waiting for the tests, which may not finish either way.)