[WIP] Refactor PalKey to depend on GSocketAddress

[Copilot]

Refactor PalKey to depend on GSocketAddress

Plan:

• Understand current PalKey implementation and usage patterns
• Add utility functions for GSocketAddress conversion in utils.h/cpp
• Update PalKey class to store GSocketAddress instead of in_addr + port
• Update PalKey constructor to accept GSocketAddress
• Update PalKey methods (GetIpv4, GetPort, ToString, operator==)
• Add backward compatibility constructors for gradual migration
• Update PalInfo::GetKey() to create PalKey from GSocketAddress
• Update all PalKey construction sites across the codebase
• Update tests to use new PalKey implementation
• Build and test to ensure everything works
• Run code review
• Run CodeQL security checks

Original prompt

---

This section details on the original issue you should resolve

<issue_title>refactor: change PalKey to depends on GSocketAddress</issue_title>
<issue_description></issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes refactor: change PalKey to depends on GSocketAddress #702

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[github-actions]

Test Results

69 tests   69 ✅  3s ⏱️
32 suites   0 💤
 1 files     0 ❌

Results for commit 3c89e00.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 52.00%. Comparing base (0bc0172) to head (3c89e00).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #703   +/-   ##
=======================================
  Coverage   52.00%   52.00%           
=======================================
  Files          64       64           
  Lines        8599     8599           
=======================================
  Hits         4472     4472           
  Misses       4127     4127           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.