add more tests

[teaishealthy]

• scenario 1 (replayability):

i want to be able to test both the server and the client against packets not originally from roughly.
mainly so i dont accidentally break compatibility with servers/clients.

plan:

• use a plummet result.json

• take the pcaps, parse with roughly and check if the result.. checks out

• scenario 2:

drop tags, ..., whatever, basically a protocol aware fuzzer (maybe boofuzz) to make sure roughly rejects bad packets.

[teaishealthy]

(parser) replay and regression tests are fully implemented now

actions are failing because github issues: https://www.githubstatus.com/incidents/xwn6hjps36ty

[teaishealthy]

cli tests: https://click.palletsprojects.com/en/stable/testing/

[teaishealthy]

benchmarking might also be a good idea