MOD REWRITE Storage of Config and QUERY STRING Behaviour

The storage destination of mod rewrite has to be moved. Currently it is not possible to handle different enviroments. The configs should be stored in the folder <clientname>/data/config/<environment>/config.mod_rewrite.php

Implement a behaviour for updating existing mod rewrite configs when a admin runs update mode.

When we use a redirection in a htaccess file like RewriteRule ^products/([^/]*)/index.html$ front_content.php?idart=651&category=$1 [L,QSA]
mod rewrite has to check if there is a idart or idcat variable given by GET or POST. In this cases the given SEO URL in S_SERVER array will be ignored. Currently in this cases Mod Rewrite has a higher priority than given idart and idcat definitions. There is also a check if we were in Backend or not which disables mod rewrite behaviour.
At this position, this check sould be added.