Policy for app id discrepencies

So far there are a few cases where app IDs aren't in alignment between upstream appstream file, Flathub's ID, and/or Fedora's ID.

• gnumeric: upstream appstream file uses org.gnumeric.gnumeric, Flathub uses org.gnumeric.Gnumeric
• mpv: upstream appstream file uses io.mpv.mpv, Flathub uses io.mpv.Mpv

In both these cases, rename-appdata-file is used, and it seems flatpak-builder will always (?) change the appstream's id to match the flatpak's, where flatpak-module-tools' will only do so sometimes? The result is Warning: No matching appdata for <flatpak-id> during install, and F: Invalid id org.gnumeric.gnumeric in flatpak build-import-bundle commands (e.g. with subsequent flatpak-module install's).

• libreoffice: upstream appstream file the pseudo-old style org.libreoffice.LibreOffice.desktop (where .desktop refers to the menu file name, not meant to be part of the app id)

Not sure if this is related, but the Fedora flatpak libreoffice does not show an icon or version information in flatseal, where the flathub one does.

• xca: no upstream appstream file, but MacOS plist is de.hohnstaedt.xca, Flathub uses io.github.chris2511.xca

I complied with Flathub's naming when creating the Fedora flatpak. Was that the right decision? Should it be changed in general?

• firefox: Flathub uses org.mozilla.firefox, Fedora uses org.mozilla.Firefox

Is this intentional? Should this be changed?