Publish F8N for FDB API versions other than 730

[melgenek]

The FDB API version is currently hardcoded to version 730 https://github.com/melgenek/f8n/blob/main/pkg/drivers/fdb/fdb.go#L65
Some lower versions might work as well, so the version has to be configurable:

1. the version needs to become a build-time variable
2. images should be produced for multiple API version, bundling FDB client libraries of a specific version
3. test pipelines should run for each of the versions.

[melgenek]

@danielfoehrKn, you mentioned that you tried running F8N with an FDB of a different API version.
Could you, please, share which version? Do you need to have an image for a version other than 730?

[danielfoehrKn]

I ran the FoundationDB cluster with 7.1.XX. I then tried to add the fdb client shared libraries for 7.1 to the K8s pod that runs f8n (via sidecars dynamically) but didn't have success with that (don't have the exact error message any more, but essentially complained about missing functions in the shared library).

AFAIK, in theory, the client library used by f8n (multi version client) should pick up a matching version from the available shared libraries.

For the testing, I then made sure to have matching f8n and fdb versions and that worked.

[melgenek]

I see. F8N doesn't use the multi version client. I would prefer keeping it this way and publishing multiple containers with prebundled FDB client libraries.
It seems complicated to ask users to have a mounted directory with FDB dynamic libs. It is probably understandable for pods, but I envision running F8N outside kubernetes in plain containers as well.