MGMT-16037: fix messaging errors on big clusters

[rccrdpccl]

When creating big clusters, we get kafka complaining about message size.
This should never happen: clusters should keep installation even if messaging fails.
Also, the message should never be this big. This PR attempts to address both issues.

List all the issues related to this PR

• New Feature
• Enhancement
• Bug fix
• Tests
• Documentation
• CI/CD

What environments does this code impact?

• Automation (CI, tools, etc)
• Cloud
• Operator Managed Deployments
• None

How was this code tested?

• assisted-test-infra environment
• dev-scripts environment
• Reviewer's test appreciated
• Waiting for CI to do a full test run
• Manual (Elaborate on how it was tested)
• No tests needed

Checklist

• Title and description added to both, commit and PR.
• Relevant issues have been associated (see CONTRIBUTING guide)
• This change does not require a documentation update (docstring, docs, README, etc)
• Does this change include unit-tests (note that code changes require unit-tests)

Reviewers Checklist

• Are the title and description (in both PR and commit) meaningful and clear?
• Is there a bug required (and linked) for this change?
• Should this PR be backported?

[openshift-ci-robot]

@rccrdpccl: This pull request references MGMT-16037 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.15.0" version, but no target version was set.

In response to this:

When creating big clusters, we get kafka complaining about message size.
This should never happen: clusters should keep installation even if messaging fails.
Also, the message should never be this big. This PR attempts to address both issues.

List all the issues related to this PR

• New Feature
• Enhancement
• Bug fix
• Tests
• Documentation
• CI/CD

What environments does this code impact?

• Automation (CI, tools, etc)
• Cloud
• Operator Managed Deployments
• None

How was this code tested?

• assisted-test-infra environment
• dev-scripts environment
• Reviewer's test appreciated
• Waiting for CI to do a full test run
• Manual (Elaborate on how it was tested)
• No tests needed

Checklist

• Title and description added to both, commit and PR.
• Relevant issues have been associated (see CONTRIBUTING guide)
• This change does not require a documentation update (docstring, docs, README, etc)
• Does this change include unit-tests (note that code changes require unit-tests)

Reviewers Checklist

• Are the title and description (in both PR and commit) meaningful and clear?
• Is there a bug required (and linked) for this change?
• Should this PR be backported?

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[codecov]

Codecov Report

Merging #5628 (7e72915) into master (9aef355) will increase coverage by 0.00%.
The diff coverage is 93.33%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #5628   +/-   ##
=======================================
  Coverage   67.72%   67.73%           
=======================================
  Files         232      233    +1     
  Lines       34201    34211   +10     
=======================================
+ Hits        23164    23174   +10     
- Misses       8976     8977    +1     
+ Partials     2061     2060    -1     

Files	Coverage Δ
internal/bminventory/inventory.go	70.29% <100.00%> (+0.02%)	⬆️
internal/stream/utils.go	100.00% <100.00%> (ø)
internal/usage/manager.go	72.50% <100.00%> (+0.70%)	⬆️
internal/cluster/common.go	76.36% <66.66%> (-0.33%)	⬇️

... and 1 file with indirect coverage changes

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 9aef355 and 2 for PR HEAD bd60682 in total

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adriengentil, gamli75, rccrdpccl

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [adriengentil,gamli75,rccrdpccl]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[rccrdpccl]

/retest

[openshift-ci]

@rccrdpccl: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[rccrdpccl]

/cherry-pick cloud_hotfix_releases

[openshift-cherrypick-robot]

@rccrdpccl: new pull request created: #5631

In response to this:

/cherry-pick cloud_hotfix_releases

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.