[6.16.z] ContentCredentials CLI fix for stream

[Satellite-QE]

Cherrypick of PR: #15165

Problem Statement

In Stream runs, for ContentCredentials, we see some occasional failures in several tests,
that attempt to add/update gpg key associated to repo/product with repo(s), then read info of the product/repo and assert the key name:

   ... setup custom repo, GPG key, add key to repo or repo's product,
        or update a GPG key already added to repo(s)

   repo = target_sat.cli.Repository.info({'id': repo['id']}) 
   assert repo['gpg-key'].get('name') == new_name
E   KeyError: 'gpg-key'

Solution

We need to wait for an in-progress Repository Metadata Generate task,
that is not handled synchronously by cli .update or cli .info. Else, the GPG key is not yet present in repo/product.

In any CLI tests adding/updating a GPG key associated to repo, or adding the key to a product containing repos,
we should wait for these repo metadata task(s), before calling info of product/repo, and asserting the key.

Related Issues

• Intermittent Stream CLI failures in ContentCredentials, el8 and el9.
• 1-3 of the affected tests inconsistently fail for same KeyError. Locally reproduced when full cli module is run.
• The metadata task is one per repo with the key added, and typically lasts 3 seconds or less,
  but it is enough for an intermittent failure when trying to read the entity (repos or product) and find the key, before the task(s) finished.

PRT Case

trigger: test-robottelo
pytest: tests/foreman/cli/test_contentcredentials.py

[Satellite-QE]

trigger: test-robottelo
pytest: tests/foreman/cli/test_contentcredentials.py

[Satellite-QE]

PRT Result

Build Number: 7193
Build Status: SUCCESS
PRT Comment: pytest tests/foreman/cli/test_contentcredentials.py --external-logging
Test Result : ================ 84 passed, 242 warnings in 1392.59s (0:23:12) =================