feat(insights): use separate deployment for Insights

[ebaron]

Welcome to Cryostat! 👋

Before contributing, make sure you have:

• [ ] Read the contributing guidelines
• [ ] Linked a relevant issue which this PR resolves
• [ ] Linked any other relevant issues, PR's, or documentation, if any
• [ ] Resolved all conflicts, if any
• [ ] Rebased your branch PR on top of the latest upstream main branch
• [ ] Attached at least one of the following labels to the PR: [chore, ci, docs, feat, fix, test]
• [ ] Signed all commits: git commit -S -m "YOUR_COMMIT_MESSAGE"

  ---

Fixes: #961 Depends on: https://github.com/cryostatio/cryostat-agent/issues/510

Description of the change:

• Removes Go module dependency on the Runtimes Inventory Operator
• Adds a Kustomize overlay to optionally build a bundle that includes a second deployment for the Runtimes Inventory Operator container image with its own RBAC
• Bumps Kustomize version to support Replacements

Motivation for the change:

• Removes a Go module dependency that is only useful in downstream Red Hat builds
• When enabled. the Insights integration no longer counts towards Cryostat Operator's resource limits

How to manually test:

1. make bundle bundle-build ENABLE_INSIGHTS=true
2. Deploy an agent sample app with -Drht.insights.java.debug=true
3. Check for a line in the agent log like: Red Hat Insights - Payload was accepted for processing

[ebaron]

/build_test

[github-actions[bot]]

/build_test completed successfully ✅. View Actions Run.