chore: Updated demos and readmes for wheel release

[frayle-ons]

resolves #128

✨ Summary

These changes add more detailed instructions for each DEMO notebook, on how to set up the virtual environment with UV or PIP and install from wheel reversion release with the appropriate optional dependency installs for each notebook. It also adds some additional setup requirements around DEMO datasets, ipykernel and how to access those

📜 Changes Introduced

• chore: updated demo notebooks with new installation section and instructions
• chore: updated readme with installation section now containing wheel release install path
• chore: updated DEMO readme with context about installation instructions for each notebook

✅ Checklist

• Code passes linting with Ruff
• Security checks pass using Bandit
• API and Unit tests are written and pass using pytest
• Terraform files (if applicable) follow best practices and have been validated (terraform fmt & terraform validate)
• DocStrings follow Google-style and are added as per Pylint recommendations
• Documentation has been updated if needed

🔍 How to Test

Trying out the demo notebooks and following the corresponding instructions, possibly in a fresh folder environment with just the single ipynb file downloaded would be good a good way to determine if the instructions are sufficient for user to follow through and acquire any additional data that is needed

[frayle-ons]

Key consideration @Tom-Owen-ONS for your review:

currently there's a lot of duplication in that roughly the same install instructions section is in every notebook. Whereas we could put one set of install instructions in the /DEMO/readme.md so that the notebooks have less content.

However, if we keep it the way it is currently proposed then the notebooks are much more self-contained, i.e. the user doesn't need to download the whole DEMO folder, and each notebook has complete instructions on how it should be run.

[Tom-Owen-ONS]

Key consideration @Tom-Owen-ONS for your review:

currently there's a lot of duplication in that roughly the same install instructions section is in every notebook. Whereas we could put one set of install instructions in the /DEMO/readme.md so that the notebooks have less content.

However, if we keep it the way it is currently proposed then the notebooks are much more self-contained, i.e. the user doesn't need to download the whole DEMO folder, and each notebook has complete instructions on how it should be run.

I think for notebooks I prefer having the installation instructions inside as they are: I kind of see them as self-contained and data scientists/testers who use them might treat them more like that as well.

[Tom-Owen-ONS]

Notebooks all run on a cloud workstation for me and the updated docs make sense (just the little note on the README that is up to you to be honest). Haven't tried on an on-net due to issues we discussed.

Thanks for this!

[Tom-Owen-ONS]

looks great!