Fix Null Reference to HostContext in GlibcCompatibilityInfoProvider

[rishabhmalikMS]

Context

Resolve null reference issue in GlibcCompatibilityInfoProvider. The issue occurs when HostContext is not properly initialized during dependency injection, causing potential failures in glibc compatibility checks.
AB#2353979

---

Description

Improved initialization of GlibcCompatibilityInfoProvider by properly implementing AgentService initialize method and correcting constructor flow.

Key Changes:

1. Improved GlibcCompatibilityInfoProvider initialization - Ensured proper AgentService inheritance with base.Initialize(hostContext)
2. Used inherited HostContext property - Leveraged inherited HostContext property from AgentService base class
3. Updated test constructors - Fixed unit tests to match corrected constructor patterns

---

Risk Assessment (Low / Medium / High)

Assess the risk level and justify your assessment. For example: code path sensitivity, usage scope, or backward compatibility concerns.

---

Unit Tests Added or Updated (Yes / No)

Yes, updated test constructors as base class constructors is updated.

---

Additional Testing Performed

Tested with pipeline run for this scenario as well
https://dev.azure.com/surajitshil/Node-24-upgrade/_build/results?buildId=812
https://dev.azure.com/rishabhmalikOrg/Test%20Project/_build/results?buildId=2370&view=logs&j=12f1170f-54f2-53f3-20dd-22fc7dff55f9&t=944b7e9c-00d2-5ab3-4f94-8de8fe321ef4

---

Change Behind Feature Flag (Yes / No)

This is behind exsiting feature falg currently.

---

Tech Design / Approach

• Design has been written and reviewed.
• Any architectural decisions, trade-offs, and alternatives are captured.

---

Documentation Changes Required (Yes/No)

Indicate whether related documentation needs to be updated.

• User guides, API specs, system diagrams, or runbooks are updated.

---

Logging Added/Updated (Yes/No)

• Appropriate log statements are added with meaningful messages.
• Logging does not expose sensitive data.
• Log levels are used correctly (e.g., info, warn, error).

---

Telemetry Added/Updated (Yes/No)

• Custom telemetry (e.g., counters, timers, error tracking) is added as needed.
• Events are tagged with proper metadata for filtering and analysis.
• Telemetry is validated in staging or test environments.

---

Rollback Scenario and Process (Yes/No)

• Rollback plan is documented.

---

Dependency Impact Assessed and Regression Tested (Yes/No)

• All impacted internal modules, APIs, services, and third-party libraries are analyzed.
• Results are reviewed and confirmed to not break existing functionality.

[rishabhmalikMS]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).