Try to onboard package(s) of FAS user than for Fedora downstream automation

[lbarcziova]

Followup of #2227

• [x] check whether the maintainer already uses Packit, if yes, contact them and ask about the feedback, offer help with setting up Packit for their other packages

If no:

• [x] contact the maintainer (Matrix/Slack/email), introduce Packit downstream automation and ask if you could create a PR with Packit config for one of their packages (you can ask whether they have access to the upstream repos or would be interested in having the config only in dist-git)
  • use the mail template (adjust it if needed)

After an agreement:

• [ ] check this spreadsheet for the list of packages and choose one (ideally with pending release to rebase, having Git upstream, easy to configure),
  • the spreadsheet should be updated accordingly, make sure that the package was not onboarded already (there is overlap of the packages since they can have multiple maintainers)
• [ ] create a Packit configuration setting up the Fedora downstream automation (for syncing start with one branch to not spam)
• [ ] optionally test the syncing locally (see comment)
• [ ] create a PR, try to do a test run (/packit pull-from-upstream --with-pr-config) and communicate further with the maintainer the follow-up steps (e.g. create issues if some functionality is missing, setup on more of their packages)

---

Part of #2204 epic

[lbarcziova]

Moving back to backlog for now, according to the maintainer, it is not easy to automate the update of these packages because they have a big dependency on many other components (Plasma):

I take an example from okular in rawhide. The package has a big dependency on KF6 (a lot of KF6 packages). If we want to update it to a new version, we sometimes have to update KF6 first, if packit does not handle these packages the update of okular will fail