[SC-639] Switch to pip for dependency management

[jbencook]

I like Poetry. But the safety we get from locking all dependencies is costing us too much development time. Instead, I'm proposing to switch back to pip-based installations.

Some problems:

• Adding a Python package to the environment can take upwards of 5-10 minutes
• Some dependencies fail to resolve entirely (I'm looking at you boto3)
• Some random package in the dependency tree can mess up the entire process. This PEP 440 error has been hurting us for a few weeks now.

Here's a public repo where we've successfully switched to pip. This PR codifies the change to make it standard for future pattern updates across our projects.

I'm pretty sure this will work well for us, but I am curious if you have any opinion about pip vs poetry @kevinbird15.

[kevinbird15]

I like this idea, but I never really utilized poetry so I can't really claim I did due diligence on that tool. Always good with pip though. My understanding is that you are using the setup.cfg to handle dependencies then, right?

sparrow_patterns/dependencies/templates/setup.cfg

[jbencook]

Yeah that's right. Not totally sure if that's the best way going forward, but that's how we're doing it for now.