build(drive-abci): debug docker image with grovedb visualizer and tokio console

[lklimek]

Issue being fixed or feature implemented

When building drive-abci image, we don't want to include tools like grovedb visualizer or tokio console.
However, for some use cases, we need these features.

We need to build additional debug package that will accompany normal release and contain forementioned features.

What was done?

1. Refactored docker image tag detection algorithm. Right now, only full releases will generate tags like MAJOR, MAJOR.MINOR, latest, etc.
2. Added manual workflow checkbox "Only build Drive image"
3. Fixed bug that could lead to use of wrong build of app retrieved from cache.
4. Added drive-abci debug image build that will have docker tag suffixed with -debug, for example for 1.2.3-dev.1, we build dashpay/drive-abci:1.2.3-dev.1 and dashpay/drive-abci:1.2.3-dev.1-debug.
5. By default, tokio_unstable, tokio console and grovedbg are enabled. For release builds (release cargo profile), this is changed on Dockerfile level - drive-abci builds with --no-default-features, and we use separate config file that has tokio_unstable disabled.
6. Normal images are built in release cargo profile (as previously), -debug one in dev cargo profile.
7. In drive-abci main.rs, added info log containing version info and list of enabled features, for easier debugging.

How Has This Been Tested?

Manual workflow run

https://github.com/dashpay/platform/actions/runs/10508658962

Prerelease v1.1.0-pr.2012.6

https://github.com/dashpay/platform/actions/runs/10508221419

Test of generated drive-abci image

Debug

docker run --rm -ti dashpay/drive:1.1.0-pr.2012.6-debug status
 2024-08-22T13:02:08.132339Z  INFO drive_abci: drive-abci server initializing, version: "1.1.0-dev.1", features: "console,grovedbg,mocks", rust: "1.76"

Release

docker run --rm -ti dashpay/drive:1.1.0-pr.2012.6 status
2024-08-22T13:03:19.811619Z  INFO drive_abci: drive-abci server initializing, version: "1.1.0-dev.1", features: "mocks", rust: "1.76"

Not tested

• full release

Breaking Changes

We no longer tag images with tags like 1-dev, latest-dev, etc.

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have added "!" to the title and described breaking changes in the corresponding section if my code contains any
• I have made corresponding changes to the documentation if needed

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

[QuantumExplorer]

do not merge for now

[shumkov]

I don't see where we add f

[lklimek]

I don't see where we add f

If you mean "where we add features", it's in Dockerfile lines 202-209, https://github.com/dashpay/platform/pull/2012/files#diff-dd2c0eb6ea5cfc6c4bd4eac30934e2d5746747af48fef6da689e85b752f39557R202-R209

The base branch was changed.