Feat: add non-nginx ingress support via X_FORWARDED_* header support for media-auth

[centerionware]

Feature Request

Is your feature request related to a problem or unsupported use case? Please describe.
AFAIK only nginx supports the HTTP_X_ORIGINAL_URL header which blocks traefik from working with media-auth.

Describe the solution you'd like
to fallback on HTTP_X_FORWARDED_PROTO, HTTP_X_FORWARDED_HOST, HTTP_X_FORWARDED_URI if they're found and HTTP_X_ORIGINAL_URL is not.

Describe alternatives you've considered
I don't want to switch my kubernetes ingress to nginx.

Discovery, Documentation, Adoption, Migration Strategy
Users will be able to host behind non-nginx ingresses

Do you want to work on it through a Pull Request?
I'll submit one tested working for me patch, if ya'll don't like the formatting or something ya'll feel free to modify it to your standards.

[centerionware]

Traefik Middlewares

apiVersion: traefik.io/v1alpha1
kind: Middleware
metadata:
    name: media-bucket-regex
spec: 
  replacePathRegex:
    regex: ^/media/(.*)
    replacement: /impress-docs/$1
---
apiVersion: traefik.io/v1alpha1
kind: Middleware
metadata:
  name: s3-host-sub
spec:
  headers:
    customRequestHeaders:
      HOST: "s3.example.com:192"
      Content-Security-Policy: "\"default-src 'none'\" always;"
---
apiVersion: traefik.io/v1alpha1
kind: Middleware
metadata:
 name: media-auth
 namespace: docs
spec:
 forwardAuth:
    address: >-
      https://impress.example.com/api/v1.0/documents/media-auth/
    authResponseHeaders:
      - Authorization
      - X-Amz-Date
      - X-Amz-Content-SHA256
    trustForwardHeader: true

Used by adding the annotation to an ingressMedia definition:

traefik.ingress.kubernetes.io/router.middlewares: docs-media-auth@kubernetescrd,docs-media-bucket-regex@kubernetescrd,docs-s3-host-sub@kubernetescrd