Goal:

Support Flatpak content, both "custom" and originating from Red Hat, in Satellite. Users should be able to easily import Flatpak content into Satellite, manage it, and deploy it to clients.

Acceptance Criteria:

• As a user, I should be able easily introspect flatpak index for flatpak repos scoped to "latest" tag on redhat registry (https://flatpaks.redhat.io/rhel/index/static?label:org.flatpak.ref:exists=1&tag=latest) and fedora flatpak index (https://registry.fedoraproject.org/index/static?label:org.flatpak.ref:exists=1&tag=latest)
• As a user, the introspection should create corresponding artifacts in Satellite representing the repos on the remote registry.(Remote flatpak repositories)
• As a user, I should be able to easily convert the remote flatpak repositories into Satellite repositories. 
• As a user, I should be able to easily sync Flatpak content without needing to search extensively for it in the UI
• As a user, I should be able to deploy Flatpak content to hosts without needing to define custom remote execution logic
• As a user, I should be able to identify Flatpak content from other normal container images
• As a user, import/export of flatpak content should work normally in connected/disconnected environments.

Open questions:

• Do we need a flatpak registry proxy controller? -> Likely.
• Do we need a smart proxy plugin? -> Container_gateway
• Does flatpak cli support user login to remote or passing certs when fetching content.