resolves #970 use cargo.toml to install svgbob

[ssaraswati]

Addresses #970 by converting the build-static-svgbob to use a Cargo.toml file instead of specifying version directly

I wasn't able to get a full build of kroki to run on my machine but this did seem to work correctly with COPY --from=kroki-builder-static-svgbobs:latest /home/rust/.cargo/bin/svgbob /usr/bin/svgbob from server/ops/docker/jdk11-alpine/Dockerfile

[ggrossetie]

Thanks for taking care of this issue 👍🏻
I left a few comments but it looks very good.

I wasn't able to get a full build of kroki to run on my machine

Let's see what the CI says.

[ssaraswati]

Thanks for taking care of this issue 👍🏻 I left a few comments but it looks very good.

I wasn't able to get a full build of kroki to run on my machine

Let's see what the CI says.

HI @Mogztter from the failed CI run it doesn't look like my initial approach is likely to work. I have taken a second go doing this via SED to extract the svgbob_cli version from the Cargo.toml file instead.

This approach seems to work fine with Renovate and doesn't require the full Cargo.toml file values to be specified. I have run a copy of renovate against it on my fork and PR was created with new svgbob versions https://github.com/ssaraswati/kroki/pull/3/files