NETOBSERV-1340: Add operator to "Networking" category in OperatorHub

[stleerh]

There is a request to also add Network Observability to the "Networking" category.

See #440 for related details.

[openshift-ci-robot]

@stleerh: This pull request references NETOBSERV-1340 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 story to target the "4.15.0" version, but it targets "netobserv-1.5" instead.

In response to this:

There is a request to also add Network Observability to the "Networking" category.

See #440 for related details.

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

All modified and coverable lines are covered by tests ✅

Comparison is base (87a34ad) 54.92% compared to head (989d35c) 54.92%.
Report is 25 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #451   +/-   ##
=======================================
  Coverage   54.92%   54.92%           
=======================================
  Files          47       47           
  Lines        6382     6382           
=======================================
  Hits         3505     3505           
  Misses       2635     2635           
  Partials      242      242           

Flag	Coverage Δ
unittests	54.92% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jotak]

/lgtm

[jotak]

@stleerh : I had to revert your previous PR adding to Observability category, as this isn't a recognized category.
Do you know if there is an ongoing change somewhere (OLM?) to create this category? I guess we need first to have this category created before we can add it here - not doing so generates validation failures (unstable downstream builds).

Adding to "Networking" is fine I guess, since this category already exists; you'll need to rebase the PR to fix conflict though

[jotak]

(I resolved the conflict via github)

[jotak]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jotak

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 [jotak]

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