Add a `tmt` test for running dfuzzer

[thrix]

The project could provide a simple tmt based test that could test any message bus, interface, or object method based on given parameters. This test could be used:

• as a very easily usable integration test for any RHEL, Fedor and CentOS Stream component
• a sanity test for dfuzzer itself

[evverx]

a sanity test for dfuzzer itself

@thrix I wonder if the dfuzzer package is going to be built on various architectures somewhere along the way? Can it replace Packit? If so I'd just close evverx#1.

[evverx]

Just to clarify I have no idea how tmt works but looking at https://github.com/matusmarhefka/dfuzzer/pull/13#issuecomment-1102613076 I kind of assumed that it can be integrated into the CI here on GitHub.

[matusmarhefka]

@evverx Packit will first build RPMs and these will be tested using tmt tests on Testing Farm. Btw I've installed Packit service into the repository.

[evverx]

Thanks! I've just opened https://github.com/matusmarhefka/dfuzzer/pull/22 and judging by "Namespace is not allowed!" Packit hasn't been fully turned on yet in the sense that the repository hasn't been approved yet. It should take a couple of days as far as I can remember.

[thrix]

I can push that :)