gh-404: Implement mochi class emulator

[LisaGoh]

🚀 Pull Request Checklist

✅ Summary

This PR solves issue #404.

🔄 Changes

Incorporated an emulator for the linear power spectrum calculated by mochi_CLASS (the mochiCLASSEmuLinearPerturbations class), trained using Cosmopower. Currently, it is implemented for the stable basis parametrisation of Lombriser et al. 2019 (varying s, a0, a1) + w0wacdm background (w0,wa), for fixed cosmology parameters (Planck 2018 fiducial). It currently only returns the linear matter power spectrum (no sigma8, nor fsigma8).

🛠 How to Test

📝 Documentation

• This PR updates documentation
• This PR does not require documentation changes
• Issue created for documentation update: Don't forget to link the task!

🏗 Related Issues

Resolves #404

📸 Screenshots (if applicable)

📌 Additional Notes

---

✅ PR Checklist for Developers

• I have titled this PR before merging as "gh-#:", where "#" represents the task it closes
• I have run locally pre-commit using pre-commit run --all-files
• I have tested my changes locally
• No new warnings or errors introduced
• I have updated documentation (if applicable)
• My changes do not introduce breaking changes (i.e: the package still gets installed)
• I have added unit tests (if applicable)
• I have consistently updated the GitHub information for the project, including milestones, task types, and other relevant details.

✅ PR Checklist for Reviewers

• The next PR targets the correct branch
• CI tests have run and passed for the latest commit on the source branch
• Check that the code can still be installed if new packages are imported
• If necessary, the notebooks in the playground will be updated in a corresponding follow-up PR
• Coverage percentage is retained or increased
• Quality of new/changed code is acceptable
• Quality of new/changed unit tests is acceptable
• No data files have been included in the commits
• Implementation follows the agreed task description point by point
• Check that any added folder/file has been added to the README.md file
• Check that the documentation has been updated accordantly
• Check that the corresponding branch has been deleted after merging. If not, delete it

[gcanasherrera]

This needs to be updated when #352 is merged.

[LisaGoh]

Heyoo @gcanasherrera I've updated this branch since #352 is now closed!

[gcanasherrera]

@LisaGoh should we merge this or wait until the new data is ready?

[gcanasherrera]

When @LisaGoh replies, @raphkou you can take care of this one too.

[LisaGoh]

Actually now I think the implementation might change, so let's wait till we have the finalised and validated emulated boost.