Update AppStream metadata

[sebastic]

The lintian QA tool reported validation issues of the AppStream metadata for the Debian package build.

appstreamcli reported the following issues:

appstreamcli validate linux/tested/usr/share/metainfo/org.openstreetmap.josm.appdata.xml 
I: org.openstreetmap.josm:6: developer-name-tag-deprecated
E: org.openstreetmap.josm:26: screenshot-no-media
I: org.openstreetmap.josm:29: unknown-tag updatecontact
I: org.openstreetmap.josm:~: developer-info-missing

The attached patch updates the AppStream metadata following the 1.0 spec:

​https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html

[taylor.smock]

Heads up: josm-dev@… was shut down this year. I think either #josm on OFTC or https://josm.openstreetmap.de/newticket would be the appropriate replacement. I'm not 100% on that though.

[sebastic]

According to the specification ​<update_contact> only supports email addresses.

Since it's optional, dropping it might be better.

[taylor.smock]

In that case, yes, dropping it would be better.

[stoecker]

Add url type=bugtracker instead to newticket or report?

[taylor.smock]

We can probably pull most of it from ​https://github.com/flathub/org.openstreetmap.josm/blob/master/org.openstreetmap.josm.appdata.xml .

[stoecker]

The bugtracker link is wrong. Correct would be /report/12 and not /query?report=12 (which shows simply your own assigned tickets with the title of report 12 :-) But why should report 12 be used?

[taylor.smock]

I think report 12 was used since that was all core tickets (the stuff we are directly responsible for). I suppose /report/1 could have been used instead.

[taylor.smock]

In 19232/josm:

Fix #23948: Update AppStream metadata (patch by sebastic, modified)

Modifications are as follows:

• Addition of caption to screenshot
• Addition of various supplementary URLs

[stoecker]

In 19233/josm:

drop list url, see #23948

[taylor.smock]

In 19237/josm:

See #23948: Fix url type (faq to help for /wiki/Help) and add a link for contribute

This additionally adds system requirements (both required and recommended).
The memory requirements comes from downloading
39.0642941;-108.5662508;39.0654645;-108.5642928
and displaying the Mesa County GIS Valleywide 2024 imagery. This was after a GC
was triggered manually; as such, JOSM is technically usable.