jupyter-notebook dependency

[ryancoe]

Description

Fixes #40 and explicitly specifies versions for dependencies

Type of PR

• Bug fix
• Major change
• New feature

Checklist for PR

• Authors read the contribution guidelines
• The pull request is from an issue branch (not main) on your fork to the main branch in WecOptTool.
• The authors have given the admins edit access
• All changes adhere to the style guide including PEP8, Docstrings, and Type Hints.
• Added note in Changelog
• Modified the documentation if applicable
• Modified or added a new test
• All tests pass
• Documentation builds
• Reference or close any relevant issues

Additional details

Include any relevant context and describe any validation and verification efforts.

[ryancoe]

@cmichelenstrofer - I'm having second thoughts about the wisdom of pinning versions for all the dependencies... bb424fa is pretty loose with this, but I still worry that it will lead to dependency conflicts for people. There's a good discussion here: https://stackoverflow.com/questions/28509481/should-i-pin-my-python-dependencies-versions

There also some tools for getting notifications when dependencies have new versions: https://requires.io

What do you think?

[cmichelenstrofer]

@ryancoe I agree, I prefer to not specify a version unless we have to (e.g. minimum version required). If something breaks it becomes very obvious (specially with our CI tests) and we can fix it quickly. I do get that dealing with dependencies can be annoying to new Python users, though. But it is a part of Python.

[cmichelenstrofer]

I made some small changes.