Problem Description: from slack

the problem is here + UI - we are assuming that as long the system has GALAXY_COLLECTION_SIGNING_SERVICE key on the settings and the value is not None  it means the system is enabled for signing,

confirm that the UI is using the feature flag collection_signing for enabling the badges and to enable UI elements for signing collections and namespaces on all screens

I will change that flag, instead of checking for that setting key alone, it will also check for the existence of a signing service in the database. (the signing service takes care of validating the keys)

Proposed Solution: 
I propose we add 2 changes to next .z release * feature flag collection_signing will be true only if setting + signing service on database exists.

• new feature flag show_signing_badges default to False during tech preview, so customer will not be concerned about the unsigned badge, we turn that to True when feature leaves tech preview.

 
create_signatures: true
upload_signatures: true
sync_signatures: true
display_sign_badges: true