feat: generate a 'full' debian repository

[Melkor333]

Hey @beatrubi :) We might want to create a CI to have an example on how this is actually done...?

I'm also using apt-ftparchive for generating the packagelists as well (under the hood I think it uses dpkg-scanpackages

README would have to be adjusted as well 😇

[beatrubi]

Interesting approach. For me apt-ftparchive is somehow in between dpkg-scanpackages and reprepo, I would have a hard time to choose my preferred one. What would be your preference? 🤔

Anyway, as I wanted to show how easy repos are, I'm struggling to expand this demo with further complexity. Basically I used https://beatrubi.github.io/ to give my audience a better understanding of Foreman/Katello's internas 😅

[Melkor333]

My view on this is:

• If you generate the repo "on the fly" in a CI (no access to pre-existing repodata) and then put it into a remote location - or you only deal with a single package - I'd prefer something somewhat easily digestible like the script from this PR. The salsa-ci people actually use aptly to generate a repo on the fly, which I find a bit ugly, but I guess also works.
• If you have a server that you keep modifying, then reprepro could be the easiest, with the exception that it can only deal with a single version per package (which IMO is a dealbreaker. You should be able to downgrade by fetching the old package if necessary). There is a new version which can deal with this, but it's stuck in the experimental debian repo for the past 8 years or so (the only one not versioned ...+really5.3.xxx). That's why aptly is my preferred tool for a server which deals with a changing package set...