ci: add nightly performance testing, update localnet Docker image to Debian Bookworm, remove unnecessary build-jet runners.

[gzukel]

Description

ci: add nightly performance testing, update localnet Docker image to Debian Bookworm, remove unnecessary build-jet runners.

Closes: DEVOP-699

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• CI Updates

How Has This Been Tested?

The docker image has been built locally to validate it builds and tested. Need to merge to register the performance pipeline for testing.

• Tested CCTX in localnet
• Tested in development environment
• Go unit tests
• Go integration tests
• Tested via GitHub Actions
• Locally

Checklist:

• I have added unit tests that prove my fix feature works

[gartnera]

zetae2e: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by zetae2e)

e2e has glibc version missmatch issues. You need to upgrade the orchestrator too.

[lumtis]

LGTM, minor comment for changelog

[github-actions]

!!!WARNING!!!
nosec detected in the following files: .github/workflows/sast-linters.yml

Be very careful about using #nosec in code. It can be a quick way to suppress security warnings and move forward with development, it should be employed with caution. Suppressing warnings with #nosec can hide potentially serious vulnerabilities. Only use #nosec when you're absolutely certain that the security issue is either a false positive or has been mitigated in another way.

Only suppress a single rule (or a specific set of rules) within a section of code, while continuing to scan for other problems. To do this, you can list the rule(s) to be suppressed within the #nosec annotation, e.g: /* #nosec G401 */ or //#nosec G201 G202 G203
Broad #nosec annotations should be avoided, as they can hide other vulnerabilities. The CI will block you from merging this PR until you remove #nosec annotations that do not target specific rules.

Pay extra attention to the way #nosec is being used in the files listed above.