borgbackup: Fix bug #12884 - borgbackup 1.2.0 crashes on running any borg command

borgbackup: Fix bug #12884 - borgbackup 1.2.0 crashes on running any borg command

- When borgbackup was upgraded from version 1.1.17 to 1.2.0 the build was sucessfully
   completed but there was no testing feedback till after full release. It turned out
   that it did not successfully run.
- python3-packaging which had been installed for the build of borgbackup needed to also
   be available for the execution.
- When borgbackup was upgraded to 1.2.0 it was noticed that the old python3-msgpack was
   no longer needed as borgbackup used its own bundled msgpack since around version 1.1.10
   What was not seen was that in version 1.1.19 or 1.1.18 the bundled version of msgpack
   had been removed and that the newer version of python3-msgpack now needed to be
   installed but the version number has to meet the borgbackup requirements which currently
   require it to be =<1.0.3
- This patch adds the python3-packaging and python3-msgpack modules as dependencies for
   borgbackup
- The egg-info files are uncommented in the rootfile so that the borgbackup metadata can
   be found by python.
- The updated borgbackup build together with the python3-packaging and python3-msgpack
   modules were installed into a vm system using the .ipfire packages.
   Successfully initialised a borgbackup repo and ran two backups to the repo and checked
   the stats for the backup. Everything ran fine.

Fixes: Bug #12884
Tested-by: Adolf Belka <adolf.belka@ipfire.org>
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>