EZP-29237: Dropped app/Resources/views as a theme override directory

[alongosz]

See https://jira.ez.no/browse/EZP-29237 for the detailed description and reasoning.

For now going with softer change - not completely removing _override but removing app/Resources/views from the list.

[bdunogier]

Dropping by a bit late, but isn't this a BC break ?

[lolautruche]

Yes it is

[alongosz]

Kind of, but can be easily worked around by configuring:

ezdesign:
    templates_override_paths:
        - '%kernel.root_dir%/app/Resources/views'

So what we can do is either treating this as soft BC and keeping as is or: create 1.4 1.2 branch from the previous commit and making dev-master 2.0.
cc @bdunogier

Side: I see now that this package also has doc and it needs to be updated :( I'll try to do it soon.

// Edit: When I've said branch 1.4 I actually meant 1.2 ;)

[bdunogier]

create 1.4 branch from the previous commit and making dev-master 2.0.

I'm fine with that. The icing on the cake would be to find a way of informing of the upcoming change (e.g. "You're relying on global override through the app/Resources/views directory. This will be removed in version 2.0. Do X X X instead").

[glye]

Given BC issue we don't want this in 1.13 LTS, do we? 1.13 currently installs the last tag: v1.2.0. The proposed tagging seems ok.

[alongosz]

Created 1.2 branch and PR #18 with aligned doc, marked as 2.0.
About triggering some kind of warning - I'm unsure how to handle it. I could just do a @trigger_error in 1.2 but then there would be no way of solving that warning w/o upgrading Design Engine to 2.0.
I tried also to do something with overridable settings, but so far failed :/