Do not create transaction for Django "/" redirects

[antonpirker]

Problem Statement

Django does redirects from URLs with a trailing "/" to an url containing the "/" (or vice verce, depending on your config) In those cases our Integration does not know the route and creates a transaction with the raw URL. This creates a lot of cardinality.

Solution Brainstorm

Do not create transaction for those framework redirects, because there is not much happening in them and they just create noise.

[szokeasaurusrex]

I spent some time investigating this today, but will move onto other things because it seems like the solution is non-trivial. Specifically, we need to come up with a reliable way to detect when we have a Django redirect to add/remove a trailing slash, and we need to ensure the changes do not affect other WSGI frameworks (transactions are created in the WSGI integration).