Relative links in markdown files always resolve to main branch

This issue appears to me as a not resolved.

Currently, relative links work only within master branch.

E.g.

1. I have a documentation branch, where I just introduced new images. There were no images in commits tree previously.
2. I committed my changes, but all images appears to be broken.
3. I have <doc1> commit hash in my documentation branch and <master1> in my master branch.
4. All rendered images links in documentation branch should be pointing to raw <doc1> commit hash. But NO!
   They are pointing to raw <master1> commit hash. Which isn't a proper behavior.

Summary:
It is necessary to render image links according to a branch where the changes are made.
But not from master branch permanently.

Similar issues:

• BCLOUD-6315
• BCLOUD-15949