Binding tool generates dependency mappings with `/bindings` as the in-container path

[dmikusa]

When you run bt dm to generate bindings for dependency mappings, the tool will generate the internal URL relative to /bindings and that is not configurable.

If you use bt args and the shell integrations then this is not an issue. If you are manually adding the arguments, it means you must volume map to /bindings and set SERVICE_BINDING_ROOT=/bindings otherwise the bindings will be missed or the bindings will point to a location that does not exist, i.e. file:///bindings/... when the volume map is /platform/bindings/....

The tool should allow configuration of the internal path.