Process to trigger new docker build:

1. create branch on main repo (if needed) - eg 4.3.4-dev
2. If an XBridge version increment is needed, update src/xbridge/version.h
3. create PR request on main repo to trigger GitLab test build
4. create new branch with same name on dockerimages repo, prepending servicenode - eg servicenode-4.3.4-dev
5. run 'BUILD SERVICENODE' template builder action in dockerimages repo

Actions will run to trigger docker image build if all items are correct

Gobyte and others (eg: DASH) have "non-standard" datadir names, eg: .gobytecore (.dashcore) which results in exrproxy-env deployed wallets needing to specify config file name (and datadir name) when using the -cli tool. Thanks to community member AAV89 for pointing this out.

The image builder should use dir_name_linux as the datadir name instead of deriving it from the config name (conf_name)

@atcsecure what are we supposed to do about the dockerimages workflow not being able to push some images to DockerHub? eg: it could push blocknetdx/unobtanium but got permission errors for verge and stakecubecoin

denied: requested access to the resource is denied
Error: Process completed with exit code 1.

https://discord.com/channels/@me/814856257356824657/926450870479097917

We need a way to specify a non-standard daemon name in the command the image will run, eg: StakeCubeCoin daemon is not called stakecubecoind but sccd

• add daemon_stem field in manifest-latest.json
• add support in generate_build_files.py and ci.sh
• add support in exrproxy-env app.py
• test it with StakeCubeCoin and any "normal" coin