Update dependency puma to v6.4.3 [SECURITY] (#177)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| puma | `6.4.2` -> `6.4.3` |
[![age](https://developer.mend.io/api/mc/badges/age/rubygems/puma/6.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/rubygems/puma/6.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/rubygems/puma/6.4.2/6.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/rubygems/puma/6.4.2/6.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

### GitHub Vulnerability Alerts

####
[CVE-2024-45614](https://redirect.github.com/puma/puma/security/advisories/GHSA-9hf4-67fc-4vf4)

### Impact

Clients could clobber values set by intermediate proxies (such as
X-Forwarded-For) by providing a underscore version of the same header
(X-Forwarded_For). Any users trusting headers set by their proxy may be
affected. Attackers may be able to downgrade connections to HTTP
(non-SSL) or redirect responses, which could cause confidentiality leaks
if combined with a separate MITM attack.

### Patches
v6.4.3/v5.6.9 now discards any headers using underscores if the
non-underscore version also exists. Effectively, allowing the proxy
defined headers to always win.

### Workarounds
Nginx has a
[underscores_in_headers](https://nginx.org/en/docs/http/ngx_http_core_module.html#underscores_in_headers)
configuration variable to discard these headers at the proxy level.

Any users that are implicitly trusting the proxy defined headers for
security or availability should immediately cease doing so until
upgraded to the fixed versions.

---

### Configuration

📅 **Schedule**: Branch creation - "" (UTC), Automerge - At any time (no
schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/powerhome/power-web-development-interview).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOC44MC4wIiwidXBkYXRlZEluVmVyIjoiMzguODAuMCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Gemfile.lock

@@ -155,7 +155,7 @@ GEM
     pry-rails (0.3.11)
       pry (>= 0.13.0)
     public_suffix (5.0.1)
-    puma (6.4.2)
+    puma (6.4.3)
       nio4r (~> 2.0)
     racc (1.7.3)
     rack (2.2.9)