[logstash-bridge] Introduce GeoIp interfaces

[mashhurs]

What this PR does?

It introduces GeoIP bridge interfaces where Logstash elastic_integration plugin can utilize.

• Have you signed the contributor license agreement?
• Have you followed the contributor guidelines?
• If submitting code, have you built your formula locally prior to submission with gradle check?
• If submitting code, is your pull request against main? Unless there is a good reason otherwise, we prefer pull requests against main and will backport as needed.
• If submitting code, have you checked that your submission is for an OS and architecture that we support?
• If you are submitting this code for a class then read our policy for that.

[yaauie]

While there's a lot going on here, I'm pretty confident in the general shape and the downstream project is passing CI when pointed at these changes.

• all bridges are interfaces, and provide factory methods to create instances from bridged inputs, making the ProxyInternal-ish classes locked-down implementation details of this bridge that are not exposed to consumers of the bridge.
• we provide AbstractExternal...Bridge base classes for implementing bridged interfaces externally without needing to know about Elasticsearch-internal types.

[yaauie]

I can understand that this needs to export to org.elasticsearch.logstashbridge, but am unsure why it needs to export to com.maxmind.db, which I believe to be a dependency of this module (not dependent on this module).

I'm okay paring this off as a separate thing to chase down.

[mashhurs]

Oops! Your assumption is correct and I believe we should remove this. I will do it now as I don't see any harmful side affects to our changes.

[yaauie]

1 failing check

Check labels — Missing: [:Team]

While we're tagged Team:Logstash, the failing check is looking for a tag that begins with a : (the ES short-hand for team ownership)