chore: Adding -d:postgres flag when creating a Docker image for release and PRs

[Ivansete-status]

Description

The -d:postgres Nim flag was added in order to not build the Postgres archive driver when a new user wanted to compile the wakunode from the command line manually. However, we do want to have Postgres support on each Docker image, both in releases and in PRs.

Changes

• Addition of -d:postgres in .github/workflows/container-image.yml.
• Addition of -d:postgres in ci/Jenkinsfile.prs.
• Addition of -d:postgres in ci/Jenkinsfile.release.
• Addition of -d:postgres in .github/workflows/pre-release.yml.
• Addition of -d:postgres in .github/workflows/release-assets.yml.

[github-actions]

You can find the image built from this PR at

quay.io/wakuorg/nwaku-pr:2076

Built from a1c3076

[Ivansete-status]

Thanks @vpavlin for this recommendation 90be916 🚀 !

[vpavlin]

I believe this covers all "release" assets - images and binaries + dev/test images built from PRs

One question though - why are you using -d:postgres and not POSTGRES=1 like with ci.yml?

[Ivansete-status]

One question though - why are you using -d:postgres and not POSTGRES=1 like with ci.yml?

Thanks for the review!
The POSTGRES=1 passed to the make has the same result, i.e. adding the -d:postgres as an additional NIM_PARAMS. This PR only introduces -d:postgres directly to make itself more consistent because, for e.g., the ci/Jenkinsfile.release only accepts NIM_PARAMS.

[NagyZoltanPeter]

Thank you! It looks ok!