[3.5] Twig exception request santitisation handling

[GwendolenLynch]

• Handle nested maps & indexed arrays in RequestSanitiser
• [Tests] Broaden RequestSanitiser tests to cover more data types

Fixes #7540
Closes #7543
Closes #7175

[Boorj]

nice) +7 lines of code && +over5000 lines of tests ;) Great job, @GawainLynch !

By the way, i don't think, that it closes #7175 .. ) There was a conversation about fallback for missing 'preview' route in routing.yml

[GwendolenLynch]

By the way, i don't think, that it closes 7175 .. ) There was a conversation about fallback for missing 'preview' route in routing.yml

For the purposes of tracking what I need to, it does. What is requested isn't coming to v3 for stated reasons.

[bobdenotter]

Looks good to me, as well.

As for the edge-case @Boorj mentions: I'm also of the opinion that if you modify the routes that are marked "Edit these at your own risk". :-)

Let's

[Boorj]

I'm of the opinion : if you create a refrigerator and put a bottle of poison with a sign ’you'll probably be poisoned’ in each one, be ready that someone will be poisoned. 'routing.yml' provides convenient way to define routes, and nobody loves tons of garbage there.

Predefined routes should have a fallback, with a possibility to override them in routing.yml. It's a consistent behavior, since every Extension has getDefaultConfig(), which is overridden by extension.config.yml.

But...

@bobdenotter told that Bolt 4 will be using symfony 4, and it will have another routing. So i'm ok with that.