Bumps the docs group in /docs with 2 updates: [pymdown-extensions](https://github.com/facelessuser/pymdown-extensions) and [mkdocs-material](https://github.com/squidfunk/mkdocs-material).


Updates `pymdown-extensions` from 10.13 to 10.14.2
- [Release notes](https://github.com/facelessuser/pymdown-extensions/releases)
- [Commits](facelessuser/pymdown-extensions@10.13...10.14.2)

Updates `mkdocs-material` from 9.5.49 to 9.6.1
- [Release notes](https://github.com/squidfunk/mkdocs-material/releases)
- [Changelog](https://github.com/squidfunk/mkdocs-material/blob/master/CHANGELOG)
- [Commits](squidfunk/mkdocs-material@9.5.49...9.6.1)

---
updated-dependencies:
- dependency-name: pymdown-extensions
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: docs
- dependency-name: mkdocs-material
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: docs
...

Signed-off-by: dependabot[bot] <support@github.com>

Bumps [golangci/golangci-lint-action](https://github.com/golangci/golangci-lint-action) from 6.1.1 to 6.2.0.
- [Release notes](https://github.com/golangci/golangci-lint-action/releases)
- [Commits](golangci/golangci-lint-action@v6.1.1...v6.2.0)

---
updated-dependencies:
- dependency-name: golangci/golangci-lint-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

Netlify recently announced configurable Python versions in their build pipeline:
https://www.netlify.com/blog/announcing-configurable-python-versions-in-netlify-builds.

Make use of this and bump Python to 3.13 since dependabot is now also issuing
warnings for 3.8 EOL.

Signed-off-by: Timo Beckers <timo@isovalent.com>

Bumps [actions/github-script](https://github.com/actions/github-script) from 6 to 7.
- [Release notes](https://github.com/actions/github-script/releases)
- [Commits](actions/github-script@v6...v7)

---
updated-dependencies:
- dependency-name: actions/github-script
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

Seems like something changed with how the location header is parsed.
Use request.url instead.

Signed-off-by: Lorenz Bauer <lmb@isovalent.com>

eBPF for Windows has historically aimed to be source compatible with
libbpf API. As part of this, POSIX error codes are found in errno.h
are used to indicate errors of all kinds.

eBPF for Windows so far aimed to be source compatible with libbpf.
This includes using the same error constants (EINVAL, etc.) as libbpf.
It does this using the errno.h header supplied by the Microsoft
C runtime. Unfortunately, Windows error codes do not always use
the same value as Linux does.

Introduce a dedicated Errno type on Windows which maps errors to
the correct constant for the platform. This means that syscall.Errno
is not an alias for unix.Errno any more.

Signed-off-by: Lorenz Bauer <lmb@isovalent.com>

Use the newly added Auxv wrapper added in golang.org/x/sys/unix v0.30.0
instead of manually go:linknaming runtime.getAuxv. This also allows to
get rid of the check for malformed auxv data as it is already performed
by unix.Auxv.

Signed-off-by: Tobias Klauser <tobias@cilium.io>

Signed-off-by: Paul Cacheux <paul.cacheux@datadoghq.com>

`binary.Read` is able to directly read its result in a slice, and this
is way more efficient from a CPU and memory allocation standpoint

                        │   old.txt   │               new.txt               │
                        │   sec/op    │   sec/op     vs base                │
ParseLineInfoRecords-10   288.6µ ± 3%   141.3µ ± 4%  -51.02% (p=0.000 n=10)

                        │   old.txt    │            new.txt             │
                        │     B/op     │     B/op      vs base          │
ParseLineInfoRecords-10   128.0Ki ± 0%   128.0Ki ± 0%  ~ (p=1.000 n=10)

                        │    old.txt    │              new.txt               │
                        │   allocs/op   │ allocs/op   vs base                │
ParseLineInfoRecords-10   4098.000 ± 0%   3.000 ± 0%  -99.93% (p=0.000 n=10)

Signed-off-by: Paul Cacheux <paul.cacheux@datadoghq.com>

Move the creation of the mutableTypes copy under the read lock, so that
the access to the len of the source types is protected when
pre-allocating the maps.

Signed-off-by: Paul Cacheux <paul.cacheux@datadoghq.com>

Commit 78074c5 ("info: expose more prog jited info"), which made its
way into v0.17.0, resulted in random runc CI failures when running i386
binary on an amd64 kernel (see [1]).

Apparently [2], the kernel always returns 64-bit pointers, so uint64
(rather than uintptr) should be used for ksyms slice regardless of
the platform to avoid the buffer overrun.

Now, to keep the public API of (*ProgramInfo).JitedKsymAddrs intact,
convert those addresses back to uintptr, as it was done before
commit 78074c5. Except, if the kernel address won't fit into an
uintptr (as it is the case when running i386 binary on an amd64 kernel),
return an empty slice and a false, rather than incorrect addresses.

[1]: opencontainers/runc#4594
[2]: https://github.com/torvalds/linux/blob/2014c95afecee3e76ca4a56956a936e23283f05b/kernel/bpf/syscall.c#L4840-L4846

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>