Update npcap to 1.80

[fearful-symmetry]

Updates npcap to version 1.80. I'm reading the docs about updating npcap, and I don't quite get this comment:

Make sure the PR adding this is back-ported to the Go versions required by the Packetbeat CrossBuild target in the mage file

Is the go version in .go-version. linked to golang-crossbuild in some way? Do I need to backport this PR to some version that matches the go version used by beats?

[mergify]

This pull request does not have a backport label. Could you fix it @fearful-symmetry? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d is the label to automatically backport to the 1./d branch. /d is the digit
  NOTE: backport-skip has been added to this pull request.

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 8503b51

cc @fearful-symmetry

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 8503b51

cc @fearful-symmetry

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 8503b51

cc @fearful-symmetry

[cmacknz]

Is the go version in .go-version. linked to golang-crossbuild in some way? Do I need to backport this PR to some version that matches the go version used by beats?

Yes there is a crossbuild container release per Go version https://github.com/elastic/golang-crossbuild/releases. The main branch is the current Go minor (1.23) and there is a branch for each previous one (1.22, 1.19, etc.)

[cmacknz]

When you merge this without backporting I thin it will only be usable for repositories that build with Go 1.23.

[fearful-symmetry]

@cmacknz alright, added the backport label, we should be good?

[cmacknz]

I think so, I am not 100% sure what happens to the container tags, the best outcome is they are republished with the npcap version bumped. You'll have to watch for that.

[fearful-symmetry]

@Mergifyio backport 1.22.8.x

[mergify]

backport 1.22.8.x

✅ Backports have been created

• Backport to branch 1.22.8.x not needed, change already in branch 1.22.8.x

[v1v]

I think so, I am not 100% sure what happens to the container tags, the best outcome is they are republished with the npcap version bumped. You'll have to watch for that.

https://github.com/elastic/golang-crossbuild/blob/main/NPCAP.md explains the steps that are required