Need to upload dependency image as public if user mark imported apps as public

[Anastasia Kuznetsova]

Steps to reproduce:
1) Log in web UI as an admin user of some tenant
2) Navigate to Murano > Manage > Package Definitions
3) Import some app (from app storage ) that has an image as a dependency
4) Navigate to Project > Compute> Images, wait until image will be uploaded and notice that public=No
5) Log out from this tenant and log as admin user from another tenant
6) Navigate to Murano > Manage > Package Definitions - user will see all public apps
7) Navigate to Project > Compute> Images - user won't see dependency image that is needed for uploaded earlier public app

Expected result:
Image should be public too, otherwise in some cases user has to make some 'extra' manipulations to reach successful deployment of some apps.
For example, part of murano apps (by the current moment) have hardcoded image's name and user from another tenant (who didn't upload package) has to upload image to his tenant with 'hardcoded' name, otherwise deployment of murano env with its app will fail with Validation error

[Kirill Zaitsev (kzaitsev)]

I disagree, that the image should be automatically uploaded as public.

We should give user control, as described in https://blueprints.launchpad.net/murano/+spec/better-package-dependency-ui

[Ekaterina Chernova (efedorova)]

Also, in dashboard making public means modifying package, since package is uploaded as non-public by default and on second wizard step user modifies some parametric.

For now, we can add a message that user have to make sure image is public when public parameter is changed

[Kirill Zaitsev (kzaitsev)]

Still think, we should implement https://blueprints.launchpad.net/murano/+spec/better-package-dependency-ui but kid of OK with having public by default

[Serg Melikyan (smelikyan)]

>but kid of OK with having public by default
I think we should start by making it public by default and then work in the feature.