Add support for separate repack scheduler DB to `cta-admin dr ls` and `cta-admin version` outputs

https://gitlab.cern.ch/cta/operations/-/issues/1565

We now have:

[root@ctapreproductionfrontend12 ~]# cta-admin dr ls
         library                    drive     host desired request status  since vid tapepool vo files data MB/s session priority activity age reason
    IBMLIB1-LTO9     IBMLIB1-LTO9-F12C3R2 tpsrv073      Up       -   Free 510263   -        -  -     -    -    -       -        0        -   9 -
  IBMLIB3-TS1160   IBMLIB3-TS1160-F14C1R2 tpsrv030      Up       -   Free 775011   -        -  -     -    -    -       -        0        -   3 -
  IBMLIB4-TS1160   IBMLIB4-TS1160-F08C2R2 tpsrv020      Up       -   Free 780986   -        -  -     -    -    -       -        0        -   2 -
SPECTRALIB1-LTO9 SPECTRALIB1-LTO9-F05B1S1 tpsrv426    Down       -   Down 780974   -        -  -     -    -    -       -        0        -   3 [cta-taped] ERROR EmptyDriveProbe: Could not [...]

which does not reflect anywhere which of the tape servers is running its daemons with which scheduler backend.

This output is currently generated based on information from the Catalogue's DRIVE_STATE and LOGICAL_LIBRARY tables calling getTapeDrives() and from DRIVE_CONFIG table calling getTapeDriveConfigs()

Operators wish to have the value of general ScheculerBackendName key of the taped config file printed in a separate column of the cta-admin dr ls output.

For the cta-admin version command we have:

[root@ctacli /]# cta-admin version
CTA Admin Client xrd-ssi-protobuf CTA Frontend Server xrd-ssi-protobuf Catalogue schema                                      DB connection string     Status
    5-dev                     dev        5-dev                     dev             15.0 postgresql:postgresql://cta:******@postgres-catalogue/cta PRODUCTION

Operators wish to have the scheduler backend name printed in one extra column to know which scheduler the frontend is configured against (cta.schedulerdb.scheduler_backend_name).