Add monitoring.yaml to hunspell-* and hyphen-* dictionary packages

[Abdifatah2023]

Summary

Adds monitoring.yaml to 7 spell-checker and hyphenation dictionary packages that were missing it, enabling automated release and CVE monitoring. Part of #4121.

hunspell-fr — Anitya ID 130209 (grammalecte), no CPE
hunspell-it — Anitya ID 390712, no CPE
hunspell-pt-br — Anitya ID 390759, no CPE
hunspell-ru — Anitya ID 390761, no CPE
hunspell-sl — Anitya ID 390767, no CPE
hyphen-de — Anitya ID 390754, no CPE
hyphen-fr — Anitya ID 390769, no CPE

Test Plan

Verified each monitoring.yaml is valid YAML
Confirmed all Anitya IDs resolve at https://release-monitoring.org
Checked NVD CPE database for each package; none have CVE entries

Checklist

• Package was built and tested against unstable
• This change could gainfully be listed in the weekly sync notes once merged
• I agree to license this contribution and all my previous contributions under the licensing terms in LICENSE.md and have the power and authority to grant those licenses.

[davidjharder]

Hi, did you create some of these release-monitoring entries as well? Some don't work.

[davidjharder]

At this moment Solus does not have guidelines for AI usage; so I will substitute my own: If you want human review and approval you must demonstrate that you, the person making this PR, have put some effort into manually verifying any AI outputs. You should also say, preferably in your own words, where and how AI was used.

Changes required:

• Remove "contribution readme"
• Verify the provided anitya IDs are working (return useful version info)
• Restore the PR template, including the licensing portion
• Briefly explain your use of AI

[Abdifatah2023]

At this moment Solus does not have guidelines for AI usage; so I will substitute my own: If you want human review and approval you must demonstrate that you, the person making this PR, have put some effort into manually verifying any AI outputs. You should also say, preferably in your own words, where and how AI was used.

Changes required:

• Remove "contribution readme"
• Verify the provided anitya IDs are working (return useful version info)
• Restore the PR template, including the licensing portion
• Briefly explain your use of AI

Hi. I removed the contribution_readme file and restored the PR template; sorry that I didn't notice. In terms of using AI, I initially used it to make sense of the project as a whole and if there is anything I should know prior to adding the monitoring.yaml files. And now it is only helping me write regular expressions to be used to scrape the version URLs for the releases. I see some of those projects I added to Anitya don't reflect the correct releases. I am having a hard time finding the correct version URLs; might be you can guide me there! I started out with the homepage and source links on the package.yml file for each package with a missing monitoring.yaml file. However, a lot of those links don't have releases/tags feed or version urls where Anitya can scrape the latest releases. I also searched online for appropriate Anitya upstreams; found it for a few of the packages but others either lack releases feed or I can't find them. Let me know if there are any other steps I should take to fix this issue.