fix(#1624): fix unbound variable in resync cardano node workflow

[MSzalowski]

List of changes

• Fix the following error:

sed -e "s|<DBSYNC_POSTGRES_DB>|${DBSYNC_POSTGRES_DB}|" \
	-e "s|<DBSYNC_POSTGRES_USER>|${DBSYNC_POSTGRES_USER}|" \
	-e "s|<DBSYNC_POSTGRES_PASSWORD>|${DBSYNC_POSTGRES_PASSWORD}|" \
	-e "s|<DBSYNC_POSTGRES_HOST>|${DBSYNC_POSTGRES_HOST}|" \
	-e "s|<DBSYNC_POSTGRES_PORT>|${DBSYNC_POSTGRES_PORT}|" \
	-e "s|<SENTRY_DSN>|${SENTRY_DSN_BACKEND}|" \
	-e "s|<SENTRY_ENV>|test|" \
	/home/runner/work/govtool/govtool/scripts/govtool/config/templates/backend-config.json.tpl > /home/runner/work/govtool/govtool/scripts/govtool/config/target/backend-config.json
bash: line 1: DBSYNC_POSTGRES_HOST: unbound variable
make: *** [config.mk:85: /home/runner/work/govtool/govtool/scripts/govtool/config/target/backend-config.json] Error 1

Checklist

• related issue
• My changes generate no new warnings
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the changelog
• I have added tests that prove my fix is effective or that my feature works

[placek]

As a hotfix that will work just fine.

I'm wondering wether we should review that to verify which services actualy use those ENVs

[MSzalowski]

As a hotfix that will work just fine.

I'm wondering wether we should review that to verify which services actualy use those ENVs

We are not using those ENVs so far, I've made just a placeholder for the potential usage under deployment via github actions