Archive the `puppet-catalog_diff` module

[smortex]

This module appears to be abandoned and we should probably archive it. This issue start the deprecation process described on our website:

An issue needs to be raised on the module to discuss whether it should be archived or not. [...] The decision will be made by lazy consensus (as described in our governance guidelines)

If your still rely on this module, it is time to take action!

You may want to update the supported operating systems matrix in metadata.json, verify that unit and acceptance tests exist and are passing, fix maintenance burden, etc. If you are not sure about where to start, feel free to ask for directions in this issue or through our other communication channels.

If nobody stepped-in to revive this module in a few weeks, it will be archived.

[nabertrand]

I think this issue was spawned partly due to the lack of support for recent versions of Debian despite claiming support for Debian, but I would argue that the recent commit history suggests this module has not been abandoned. There doesn't appear to much in terms of spec/acceptance testing for this module, but I do not personally have time to add this. Would it be acceptable to just update the OS list to only include supported operating systems as long as the existing tests still pass?

[smortex]

@nabertrand yes, I opened this when looking for modules that claimed Debian support but do not support "current" versions. Looking at the files in the manifests directory, the latest code change was from ~10 years ago, hence the above reason.

If people currently use this module, it indeed makes sense not to archive it! Feel free to add current OS versions to the module and we will close this issue.

There is light testing in place which is great. On my todo list I want to add very basic acceptance tests to all modules where it makes sense where we basically just include the init class and make sure that produce a working catalog. This module would then also benefit from it 😉