[hrushikesh-s]

Summary

Include a summary of major changes in bullet points:

• Tutorial tutorials/finite_temperature_phonons.ipynb, PR 6 of Plan: split the finite-temperature phonon workflow (#1560) into PRs #1585. This branch contains Add the jobs and schema of the finite-temperature phonon workflow #1600, Add the force field and VASP flows of the finite-temperature phonon workflow #1601 and [WIP] Add the docs of the finite-temperature phonon workflow #1603, which should be merged first.
• Part A runs the workflow with three MACE potentials: five materials from 100 to 900 K with and without an NPT MD, a test of the MD length and the number of snapshots on KNaICl, and Li3PS4, which is unstable at 0 K. Its cells are skipped in the notebook tests.
• Part B draws the figures and tables from the numbers of our runs, stored in tests/test_data/forcefields/finite_temperature_phonons_tutorial/ft_results.json.gz. It needs only atomate2 and runs in seconds in the notebook tests. No figures are stored in the repo.
• The tutorial is added to tutorials.md and linked from the docs.

Additional dependencies introduced (if any)

• List all new dependencies needed and justify why. While adding dependencies that bring
  significantly useful functionality is perfectly fine, adding ones that add trivial
  functionality, e.g., to use one single easily implementable function, is frowned upon.
  Justify why that dependency is needed. Especially frowned upon are circular dependencies.

• None

TODO (if any)

If this is a work-in-progress, write something about what else needs to be done.

• None

Checklist

Work-in-progress pull requests are encouraged, but please put [WIP] in the pull request
title.

Before a pull request can be merged, the following items must be checked:

• Code is in the standard Python style.
  The easiest way to handle this is to run the following in the correct sequence on
  your local machine. Start with running ruff and ruff format on your new code. This will
  automatically reformat your code to PEP8 conventions and fix many linting issues.
• Doc strings have been added in the Numpy docstring format.
  Run ruff on your code.
• Type annotations are highly encouraged. Run mypy to
  type check your code.
• Tests have been added for any new functionality or bug fixes.
• All linting and tests pass.

Note that the CI system will run all the above checks. But it will be much more
efficient if you already fix most errors prior to submitting the PR. It is highly
recommended that you use the pre-commit hook provided in the repository. Simply run
pre-commit install and a check will be run prior to allowing commits.