Remove upper bounds on dependency requirements

[thomas-bc]

Originating Project/Creator
Affected Component
Affected Architectures(s)	setup.py
Related Issue(s)	nasa/fprime#1690
Has Unit Tests (y/n)
Builds Without Errors (y/n)
Unit Tests Pass (y/n)
Documentation Included (y/n)

---

Change Description

Removing the upper bounds on dependency requirements in the setup.py in preparation for version bumps in F' core requirements.txt

Rationale

Python package versions need bumping as some are insecure. This will be done in the requirements.txt in F', but we need to loosen the requirements on fprime-tools as there are upper bounds. I chose to remove the upper bounds altogether for the following reasons:

• the usage of upper bounds is most often based on the presumption that future major versions will break untested code - a presumption that is usually incorrect
• there is really no reason to install fprime-tools by itself, so the dependency versions are controlled by fprime's requirements.txt anyways
• makes future updates easier

The only downside of this approach that I could identify is that there is a very small probability that by installing an external dependency in the virtual environment, that dependency will introduce an upgrade of one of fprime's dependency - and that upgrade might break things...
Let me know what you think

[thomas-bc]

A good argument in favor of not introducing upper bounds unless it is actually proven that existing later versions are breaking is made here python-poetry/poetry#2731 (comment)

[LeStarch]

Agreed.