EZEE-2718: Adjust tests for redirects

[mnocon]

After https://jira.ez.no/browse/EZEE-2718 the behaviour after Trashing a content item has changed:
Before:
Trashing a Content Item that has a Landing Page as a parent redirects to the Parent in Content View
After:
Trashing a Content Item that has a Landing Page as a parent redirects to the Parent:

• ezplatform: in Content View
• ezplatform-ee: in Page Builder

This is a bit tricky, as we don't have a mechanism right now to deal with logic like this.

Possible solutions:

1. the proposed one - adding an IF based on environment

I'm not a fan of this, but it works - we need to think of a better approach for future uses.

2. Defining the same step definition in two Contexts and specifying the correct one in behat_suites.yml

I've decided against at as it does not work for use cases like "I want to run AdminUI suite on ezplatform-ee (we would have to define the suite twice, with the different Context being the only difference)

3. Creating two scenarios, tagging it with ezplatform and ezplatform-ee and filtering it in suites:

Again, this does not work for use case "I want to run AdminUI suite on ezplatform-ee"

4. Creating two scenarios, tagging it with ezplatform and ezplatform-ee and filtering in an BeforeScenario hook

This works, but only partially - the ezplatform-ee scenario might require steps that are not defined in any AdminUI Context, so it will fail when running with --strict flag because of undefined steps

5. Create a Behat extension that will allow to skip tests marked with a certain tag (for example "ezplatform" when running on "ezplatform-ee") and will not mark undefined steps in these Scenarios as missing

I've an idea how to do it, but it's not something I can do right now.

[mnocon]

I've decided to use this opportunity to remove this, I don't think we need it and it causes failures from time to time.

[m-tyrala]

I'm not entirely sure what do you mean by 5. option (so I'll be happy to talk about it when you'll work on it), but fix itself is fine for me.

[micszo]

👍 to unblock tests.

[lserwatka]

@mnocon is this ready for merge?

[mnocon]

@lserwatka yes, this one can be merged

[lserwatka]

Great work! Could you merge it up?

[mnocon]

Done