PBM-1663: Rename StorageName to Profile and always Include it

[jcechace]

• Display Profile when running pbm list
• Display profile when running pbm status
• Renamed storageName to profile in json output of pbm list and pbm status
• Renamed strageName to profile in output of pbm describe-backup
• Added storageType to output of pbm describe-backup

[jcechace]

@boris-ilijic not 100% sure about this rename as it breaks backwards compatibility of the output. However we might want to unify on using "profile" instead of profile/storage (at least for user facing output)

[boris-ilijic]

Requirement is to rename output of describe-backup command. But, that's not that one. If you are referencing to that backwards compatibility, it's ok to change that imo.

[jcechace]

I know, this one is part of list/status output and the field is exposed only with json output format. That said, I think we should be consistent and use "profile" everywhere. Thus also changing it here.

The actual definition for this one is of course https://github.com/percona/percona-backup-mongodb/pull/1232/files#diff-af738542639de6b3986d91c7462ac67697ce30184538554a7764f771a4c1a942R1156

[jcechace]

@boris-ilijic this one can be reviewed, adding --profile to list and status commands will be next (as a standalone PR).

[boris-ilijic]

LGTM

[boris-ilijic]

From the ticket:

we can display the profile name and shorten it if needed (e.g., limit it to 15 characters)

Currently we have:

Backups:
========
FS  /opt/backups/pbm
  Snapshots:
    2025-12-04T08:44:05Z 606.92MB <physical, this is one long named profile let's see how it looks like> success [restore_to_time: 2025-12-04T08:44:07]
    2025-12-04T08:40:54Z 605.09MB <physical, gcs> success [restore_to_time: 2025-12-04T08:40:57]
    2025-12-04T08:39:55Z 152.79KB <logical, s3> success [restore_to_time: 2025-12-04T08:39:59]
    2025-12-04T08:39:14Z 604.08MB <physical> success [restore_to_time: 2025-12-04T08:39:16]
    2025-12-04T08:38:44Z 94.38KB <logical> success [restore_to_time: 2025-12-04T08:38:48]

Maybe we can have like this to keep compact style:

  Snapshots:
    2025-12-04T08:44:05Z 606.92MB <physical, this is one...> success [restore_to_time: 2025-12-04T08:44:07]
    2025-12-04T08:40:54Z 605.09MB <physical, gcs> success [restore_to_time: 2025-12-04T08:40:57]

But I am not sure, what do you think?

[jcechace]

We can add it, but I wouldn't expect this to be a common problem (nobody sensible is going to name their profile like that). If they do then it's not really breaking anything it will just make their output not so nice.

I actually decided to ignore that part on purpose and wanted to know if this is something you would find useful.

[boris-ilijic]

Let's keep it as it is now then.