Drop dbadger-io dependency

[dliappis]

dbadger is used as part of the add_cloudfoundry_metadata processor (dependency defined here and in go.mod).

As described in hypermodeinc/badger#2155, Badger is currently utilizing the package go.opencensus.io, which has been archived since 2023 and is no longer recommended for use. Additionally, it cannot be downloaded without the Go proxy due to an expired certificate on their site. The dependency on go.opencensus.io results in build failures as seen e.g. in https://buildkite.com/elastic/beats-xpack-metricbeat/builds/10786#01948d0d-6915-43c7-b0f0-07ef954e2ee0/134-400

It could probably be replaced with something else, probably bbolt which is already used elsewhere in beats and is what otel’s file storage extension uses.

[dliappis]

@jlind23 could you help assigning this the right Team: label?

[jlind23]

@lalit-satapathy adding this to your plate as your team owns everything cloudfoundry related.

[lalit-satapathy]

@lalit-satapathy adding this to your plate as your team owns everything cloudfoundry related.

Adding to team backlog for next sprint. CC: @stefans-elastic

[stefans-elastic]

@dliappis I've been working on this and noticed that not only badger depends on go.opencensus.io

If i'm reading go mod graph correctly then getting rid of badger wouldn't be enough to get rid of go.opencensus.io.
That being said I think we still need to get rid of badger (like you said - in other places bbolt is used, so i don't think we need to use different packages for the same job, bbolt should be enough). What do you think?

[dliappis]

@dliappis I've been working on this and noticed that not only badger depends on go.opencensus.io

If i'm reading go mod graph correctly then getting rid of badger wouldn't be enough to get rid of go.opencensus.io. That being said I think we still need to get rid of badger (like you said - in other places bbolt is used, so i don't think we need to use different packages for the same job, bbolt should be enough). What do you think?

I'd say that it's important that we get rid of badger because it's unclear if and when the opencensus dependency will be addressed. For the remaining GCP related libraries that depend on opencensus, I assume some update will happen sooner than later due to the amount of usage across the internet.
I'll defer to @cmacknz on what's the preferred direction.

[cmacknz]

Having fewer local database dependencies in Beats is a good thing regardless of the opencensus problem. If this doesn't remove opencensus by itself, there's no urgency to do it however.

[stefans-elastic]

@dliappis @cmacknz PR is ready for review - #42571