IBX-1696: Implemented Config Resolver & service container parameters rebranding

[alongosz]

Question	Answer
JIRA issue	IBX-1696
Type	feature
Target Ibexa version	v4.0.1
BC breaks	no

This PR implements Config Resolver & service container parameters rebranding add-on to ibexa:rebranding command.

• BC layer,
• Created service container parameters map
• Created Config Resolver namespaces map
• Implemented Config Resolver & service container parameters rebranding

[alongosz]

Still draft, but @Nattfarinn @ViniTou any remarks about mapping of config resolver namespaces and parameters (2 map files)?
@ciastektk included ezrecommendation config resolver namespace in the BC map.

[ViniTou]

Personally I am against separate namespace just for personalization, unless this is temporary because of the overlay of two PRs.
@ciastektk @alongosz

if anything it should be ibexa.site_access.config.personalization

[alongosz]

Personally I am against separate namespace just for personalization, unless this is temporary because of the overlay of two PRs.
if anything it should be ibexa.site_access.config.personalization

@ViniTou I think @ciastektk is gonna merge it into one. On the side note - it cannot be ibexa.site_access.config.personalization because it's reserved for: ibexa.site_access.config.<scope> and might cause a conflict when someone decides to create personalization Site Access.

[ciastektk]

Yes, I will merge both configurations into one. Most of the parameters will follow the pattern: ibexa.site_access.config.<scope>.personalization

[alongosz]

Rebranding has been finalized without a need for this. Closing as obsolete.