Add support for topic "selectors" to Kafka output

[robbavey]

What does this PR do?

This commit adds support for topic selectors to provide parity with the existing beats Kafka output - see https://www.elastic.co/guide/en/beats/filebeat/current/kafka-output.html#topic-option-kafka and https://www.elastic.co/guide/en/beats/filebeat/current/kafka-output.html#topics-option-kafka for details on how to use this function.

This PR continues to use the outil.Selector from libbeat as used in the beats Kafka output

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
  - [ ] I have made corresponding changes to the documentation
  - [ ] I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
  - [ ] I have added an entry in CHANGELOG.md or CHANGELOG-developer.md.

How to test this PR locally

Testing can be done the same way as #147, with changes for the kafka output:

Run a local Kafka running on port 9092, and using metricbeat with:

output.shipper:
  server: "localhost:50052"

And the following settings in elastic-agent-shipper.yml

output.kafka:
  enabled: true
  hosts: ["localhost:9092"]
  topics:
  - topic: "network"
    when.contains:
      metricset.name: "network"
  - topic: "process"
    when.contains:
      metricset.name: "process"
  - topic: "error"
    default:  

And using kcat to pull messages out of the various topics to prove the correctness of delivery.

kcat -b localhost:9092 -G mygroup <TOPIC_NAME>

Related issues

Closes #167

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @robbavey? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-12-08T18:46:06.036+0000

• Duration: 16 min 58 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[faec]

Thanks! This looks good as a stopgap but it makes me nervous that it expands our dependence on beat.Event, which we ultimately want to remove from the shipper. Can you open a followup issue to add "real" selector support to the Kafka output that doesn't depend on the old libbeat data structures?

[robbavey]

@faec Yeah, I agree with that - I've created #203 to track