fix: path generation in case of relative file paths without artifact directory

[geoHeil]

Resolves #362

[github-actions]

✅ DCO Check Passed

Thanks @geoHeil, all your commits are properly signed off. 🎉

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

• title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?(!)?:

[dolfim-ibm]

There is something weird here, it looks like you are duplicating the function _get_output_paths()?

[geoHeil]

There is something weird here, it looks like you are duplicating the function _get_output_paths()?

indeed - fix pushed now

[vku-ibm]

I'm not sure about this line. Depending on from where this function is called, the use case can be different:

• for example, if called from save_as_json() with image referenced flag, then one can have a use-case where images are stored completely separately from the json document itself, but path is still relative
• the other example is when both save_as_json() and save_as_markdown() used, with image referenced flag, one could use the same artifact directory to store images and avoid duplication. To clarify, an example would be filename="../results/json/my_doc.json" and filename="../results/md/my_doc.md" with a shared reference images artifacts_dir="../results/ref_images/my_doc/"

[vku-ibm]

My proposal would be to not modify artifacts_dir in any way if value is provided.