feat: add panic propagation option to gin middleware

[miguelb]

If gin middleware catches a panic it bypasses other middleware panic handlers. This is an issue in our use case because we have middleware which sends panics to our notification/alert system. The changes in this PR is modeled from other modules which support panicPropagation.

[cla-checker-service]

💚 CLA has been signed

[apmmachine]

💚 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-09-19T13:54:25.576+0000

• Duration: 59 min 32 sec

Test stats 🧪

Test	Results
Failed	0
Passed	8547
Skipped	201
Total	8748

🤖 GitHub comments

Expand to view the 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!)

[miguelb]

I did sign the contribution guidelines. Does this take some time before it gets picked up?

[axw]

@miguelb thanks for opening the PR!

It looks like your commit is not associated with the email you used to sign the CLA. I think what you need to do is configure user.email in git, recreate the commit, and force-push.

[miguelb]

/test

[axw]

Nice, thanks :)

[axw]

/test

[apmmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (59/59)	💚
Files	99.346% (152/153)	👍
Classes	96.275% (336/349)	👍
Methods	90.216% (959/1063)	👍
Lines	82.149% (11164/13590)	👎 -0.021
Conditionals	100.0% (0/0)	💚

[axw]

run elasticsearch-ci/docs