Prevent duplicate naming for providers and content views

In Modeler

• Add JSF UI dependency
• Create a toto search content view
• Create a toto page provider with a predicate having the NOT IN operator
• Deploy your configuration

=> when accessing the search form, an error 500 is triggered because of the not in operator, meaning that the page provider of the content view is overridden by the one configured in the page provider

Expected:

• Studio should have a distinct name for the underlying page provider of the content view and prevent this name from being used in a page provider
• OR page providers and content views should not be allowed to have the same name