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

[lbarcziova]

Followup of #2227

• 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:

• contact the maintainer, 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

[lachmanfrantisek]

I've created a user card to track blockers: https://github.com/packit/user/issues/17

@majamassarini , can you please send the user response with the state of their issues:

• Dependency rebuild for new versions to be synced downstream #2343
• Linking of the upstream release from dist-git PR is done.
• Link source diff (e.g. mozman/ezdxf@v1.1.2...v1.1.3). -> Ask for creating a new issue (and link it to https://github.com/packit/user/issues/17)