Design for generic artifact fetching

[kosciCZ]

Maintainers will complete the following section

• Commit messages are descriptive enough
• Code coverage from testing does not decrease and new code is covered
• Docs updated (if applicable)
• Docs links in the code are still valid (if docs were updated)

Note: if the contribution is external (not from an organization member), the CI
pipeline will not run automatically. After verifying that the CI is safe to run:

• approve GitHub Actions workflows by clicking a button
• approve the Red Hat Trusted App Pipeline container build by commenting /ok-to-test
  (as is the standard for Pipelines as Code)

[kosciCZ]

@brunoapimentel PTAL

[brunoapimentel]

Leaving some additional comments just to clarify some points, but I believe we have a solid direction to start the implementation.

[eskultety]

Nothing major just quick nitpick fixes. In general I am in agreement. With the first ideas of contributing guidelines having materialized recently we can merge this OR keep it open until the implementation work is done, update sections as necessary should some further technical considerations be made during development, etc. I'd be fine either way. That said, if you wish to merge this right away then please squash all commits into a single one, no fixups please.

[brunoapimentel]

Giving my ack here since I'm also in agreement with the design, but I'd suggest not to merge this (as Erik commented before), and turn it in an ADR when the feature is production-ready.

[lkolacek]

Giving my ack here since I'm also in agreement with the design, but I'd suggest not to merge this (as Erik commented before), and turn it in an ADR when the feature is production-ready.

+1

[lkolacek]

LGTM +1, thank you guys!

[kosciCZ]

Thanks for all your reviews, I'll keep this open and will then edit it into ADR when we're done with the implementation.

[kosciCZ]

Opened a new PR #718 that converts this content into ADR and user documentation