Implement middleware to prevent regexp parameters and payload

[bugraoz93]

closes: #47364

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[bugraoz93]

CI failures seem unrelated. Rebasing

[bugraoz93]

Okay, two tests from k8s are seems related. I will check this out to be sure, but implementation should be ready for review.

[potiuk]

I think we should be able to disable that middleware - or add exceptions. With middlewares like this, it's often to get unforeseen false positives and we should be able to give the users a chance to bypass the middlewar in such specific cases.

[bugraoz93]

I think we should enable it by default. What do you think?

[bugraoz93]

cc: @potiuk @pierrejeambrun when you have time could you please check this out? I believe it is a good feature to ship with the new release.

[pierrejeambrun]

Yes I’ll take a look.

I focused on other things before the freeze so we could push features in.

[bugraoz93]

Yes I’ll take a look.

I focused on other things before the freeze so we could push features in.

As a devtool I don’t think this is impacted by the code freeze so I though I could do this then :)

For sure, I can relate, thanks! :) It was a suggestion to maybe test more since it is fragile but definitely not impacted :)