Add a test case for flatpak CV scoping

[vsedmik]

Problem Statement

Satellite implements second endpoint for flatpak registry index which is org/CV scoped, while the default pulpcore endpoint is system-wide. We already have test cases for the pulpcore system-wide EP, but we need to test the CV scoped one too. It will probably become the default users would want to use.

Solution

This PR add an E2E test case for that CV scoped endpoint.

Related Issues

https://issues.redhat.com/browse/SAT-28677

PRT test Cases example

trigger: test-robottelo
pytest: tests/foreman/cli/test_flatpak.py -k test_sync_consume_flatpak_repo_via_cv
Katello:
  katello: 11300

[vsedmik]

trigger: test-robottelo
pytest: tests/foreman/cli/test_flatpak.py -k test_sync_consume_flatpak_repo_via_cv
Katello:
  katello: 11300

[Satellite-QE]

PRT Result

Build Number: 10153
Build Status: SUCCESS
PRT Comment: pytest tests/foreman/cli/test_flatpak.py -k test_sync_consume_flatpak_repo_via_cv --external-logging
Test Result : ========== 1 passed, 6 deselected, 19 warnings in 1780.09s (0:29:40) ===========

[synkd]

One possible typo, otherwise this looks good to me.

[synkd]

Suggested change

	# 3. Create an AK assigned with one CVE only.
	# 3. Create an AK assigned with one CV only.

I'm guessing you meant content view here, but feel free to ignore if you did mean CVE.

[jeremylenz]

I'm trying really hard not to get in the habit of using "CVE" as an abbreviation for content view environment. It may be a losing battle..

[vsedmik]

Hehe, I got the impression that "CVE" is the new fancy way to name "particular CV version promoted to particular LCE" (and it seems so nicely short and descriptive to me)

But I can step back and update the PR with something like "CV/LCE" not to spread that nice habit further. 🥲

[synkd]

@vsedmik I don't want to be too prescriptive here, but for me, using CVE to mean anything other than Common Vulnerabilities and Exposures in this context is confusing enough that it actually reduces code readability, because it's such an industry-standard abbreviation. It would be like coming up with a new meaning for TCP.

This is ultimately your decision, and if using CVE to mean content view environment is already an established practice, then I acknowledge that there's not much I can do about that. But if the habit is not fully established, then I would encourage both you and @jeremylenz to keep up the fight.

[jeremylenz]

yeah, I'm trying not to establish it :) Usually I try to type out "content view environment" fully. Or sometimes I just use "environment," but that's not ideal either because we already have about 3 meanings for that word.

[vsedmik]

Oh okay, finally got your point with the Common Vulnerabilities and Exposures parallel. Captions updated.

[vsedmik]

trigger: test-robottelo
pytest: tests/foreman/cli/test_flatpak.py -k test_sync_consume_flatpak_repo_via_cv

[Satellite-QE]

PRT Result

Build Number: 10196
Build Status: SUCCESS
PRT Comment: pytest tests/foreman/cli/test_flatpak.py -k test_sync_consume_flatpak_repo_via_cv --external-logging
Test Result : ========== 1 passed, 6 deselected, 19 warnings in 1046.59s (0:17:26) ===========