Plugin adoption: I'd like to co-maintain http-request

Hi! 👋

The `adopt-this-plugin` topic brought me here. I'd like to **adopt and co-maintain this plugin**.

**Who I am:** I recently became the maintainer of [discord-notifier-plugin](https://github.com/jenkinsci/discord-notifier-plugin) through the [Adopt-a-Plugin program](https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/) (RPU [#5271](https://github.com/jenkins-infra/repository-permissions-updater/pull/5271), with @markewaite's approval). Since taking it over I've merged a long-standing truncation bug fix ([#159](https://github.com/jenkinsci/discord-notifier-plugin/pull/159)), shipped release `281.v41a_01a_c2e7dc`, and have a dependency-modernization PR up ([#165](https://github.com/jenkinsci/discord-notifier-plugin/pull/165) — unirest-java → Apache HttpComponents swap).

**Why http-request:** it's a widely-used plugin (30k+ installations) sitting on a backlog with no active day-to-day maintainer — recent history is almost entirely dependabot bumps. My recent work maps directly onto it: the discord-notifier swap was a from-scratch migration to `CloseableHttpClient` with proxy/timeout/multipart parity, which is exactly this plugin's territory. Old PRs like #137 (proxy auth), #124 (redirect handling), and #53 (Authorization masking) are in the same problem space.

**What I'd do first:** triage the open PR queue (some date back years), work through the high-signal issues (#319 error masking, #320 secret-text credentials, #323 proxy env vars), and keep releases flowing.

@janario @markewaite @oleg_nenashev @sandi2382 @ralnoc — would any of you object, or better yet, like to hand over with your blessing? Happy to take pointers on anything load-bearing I should know about.

— h3nr1-d14z

Start by reviewing the open pull request queue and the referenced issues #319, #320, and #323, then assess the plugin's current maintenance needs. Done would mean agreement on the co-maintainer handover and a clear plan for triage, issue work, and releases.

Written by the indexing model from the issue text.