[#52] Show qualified paths in `coffer` messages

[DK318]

Description

Problem

coffer messages don't show backend name in paths. Sometimes we need it. For e.g.

coffer copy 'b1#/a' 'b2#/a'
[SUCCESS] Copied '/a/b' to '/a/b'.

It looks very odd.

Solution

Supported qualified paths in coffer messages. Now example above would print next

coffer copy 'b1#/a' 'b2#/a'
[SUCCESS] Copied 'b1#/a/b' to 'b2#/a/b'.

Related issue(s)

• Fixes #52

  Related changes (conditional)

  • Tests

    • [x] If I added new functionality, I added tests covering it.
    • [x] If I fixed a bug, I added a regression test to prevent the bug from silently reappearing again.

  • Documentation

    • [x] I checked whether I should update the docs and did so if necessary:
    • README
    • Haddock

  • Public contracts

    • [x] Any modifications of public contracts comply with the Evolution of Public Contracts policy.
    • [x] I added an entry to the changelog if my changes are visible to the users and
    • [x] provided a migration guide for breaking changes if possible

  Stylistic guide (mandatory)

  • [x] My commits comply with the policy used in Serokell.
  • [x] My code complies with the style guide.

[dcastro]

I'm starting to think Entry should have a QualifiedPath EntryPath instead of an EntryPath.

But this is outside the scope of this PR. I'll have a deeper look at this later and re-valuate where and how we should use QualifiedPath.

LGTM :+1:

[MagicRB]

Regarding the code itself, LGTM. Architecturally:

1. QualifiedPath is a weird a name, especially when specialized as QualifiedPath Entry. Imo we should rename it and maaybe add a class constraint just so the types are a bit tighter and represent more what we meant
2. I don't think Entry should take on a QualifiedPath EntryPath or such field. Two entries from two backends should be equivalent, once an entry is read, its not bound to any one backend, it just exists. Adding more data on top of it with QualifiedPath or similar is imo the right way to go