python-muranoclient can attempt to delete the wrong package when asked to update

Due to the fact, that murano now has non-unique fqpn and due to the fact, that during update python-muranoclient attempts to delete a package by name — there is a chance, that it will not delete the correct package.

To reproduce:

import 2 packages in different tennants,
attempt to import a package in one of those tennats with --exists-action=u, than in another.

It actually can be random, due to lack of any sorting done during pkg fetching.