Fix conflict between nornir and dataclasses

[dmjacobsen]

dataclasses 0.8 is getting pulled in implicitly by ... something ... in the context of a docker build. This causes the program to not operate correctly as reported in #78. One possible fix is to simply constrain the version of dataclasses to 0.7 to prevent this anomalous behavior, another would be to identify what is pulling in dataclasses and address it more explicitly elsewhere. Being unfamiliar with this package, I've chosen the former.

Summary and Scope

Description: What does this change do? Use examples of new options and output changes when possible. If other changes were made list these as well in a list.

PR checklist (you may replace this section):

• I have run nox locally and all tests, linting, and code coverage pass.
• I have added new tests to cover the new code
• My code follows the style guidelines of this project
• If adding a new file, I have updated pyinstaller.py
• I have updated the appropriate Changelog entries in readme.md
• I have incremented the version in the readme.md
• I have incremented the version in canu/.version

Issues and Related PRs

Potentially resolves #78

Testing

Tested on:

• modified buildah/podman instance of Dockerfile (will file issue on that separately) on the alvarez management VM.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[trad511]

Haven't left this behind. Looking at this in conjunction with the WIP 44 branch to reconstruct the setup.py build.

[sonarqubecloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
34.9% Duplication

[rustydb]

The unittests should've finished.. they're stuck.
The branch build won't run because this is a fork.

[rustydb]

When I look in the current build output I don't see this package brought in, neither in main nor develop.