Update filter and documentation to catch *auth*

[jaggederest]

What does this pull request do?

Sanitize anything containing the word 'auth', instead of just the complete string 'authorization'

Why is it important?

Some applications may use less than the full word authorization to transmit sensitive data that should be filtered.

Checklist

• I have signed the Contributor License Agreement.
• My code follows the style guidelines of this project (See .rubocop.yml)
• I have rebased my changes on top of the latest main branch

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

• I have made corresponding changes to the documentation
• I have updated CHANGELOG.asciidoc
• I have updated supported-technologies.asciidoc
• Added an API method or config option? Document in which version this will be introduced

Related issues

closes #1210

[ghost]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-05-19T04:48:57.413+0000

• Duration: 27 min 51 sec

Test stats 🧪

Test	Results
Failed	0
Passed	44189
Skipped	80
Total	44269

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• run benchmark tests : Run the benchmark test.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[ghost]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (1/1)	💚
Files	99.2% (124/125)	👍
Classes	99.2% (124/125)	👍
Lines	59.456% (2490/4188)	👎 -0.191
Conditionals	100.0% (0/0)	💚