fix(ci): remove target flag from docker command

[rymnc]

Description

Includes a debug flag in the jenkinsfile

Changes

• Adds the debug target, and replaces the experimental target since it doesn't exist anymore

[LNSD]

@rymnc Note that I suggested having a "debug tools" target in the Dockerfile (e.g., for an image including the heaptrack tool), and that would require it.

EDIT: Not specifying the target would mean you would build all the targets, and it would deploy the image that includes the debug tools.

cc @Ivansete-status

[rymnc]

@LNSD, thanks for the catch -
I've added an additional flag in 7013911 for the debug target, so we can rollout the debug containers to all nodes in the test fleet at once if required then, if it is unset, will use the prod image.

[Ivansete-status]

Thanks for the PR @rymnc ! However, I miss the DEBUG flag in our Makefile so that we can clearly have release by default and debug on demand.

Btw, we are generating the release binaries with debug information. We have the next for the statusteam/nim-waku:v0.16.0 package:

/ # file /usr/local/bin/wakunode2 
/usr/local/bin/wakunode2: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-musl-x86_64.so.1, with debug_info, not stripped

Was that made on purpose @jm-clius ?

[jm-clius]

Btw, we are generating the release binaries with debug information.

Mmm. There may be something here, though I think the default build will be with -d:release as it should. Release builds should contain debugger info, just with the lighter weight libbacktrace stack tracing: https://github.com/status-im/nim-libbacktrace