Add .NET client library to README

[Memphizzz]

User description

This PR adds a .NET client library to the README.

LibreSpeed.NET is a .NET Standard 2.0 library that allows measuring download speed, upload speed, ping, and jitter against LibreSpeed servers. It's available on NuGet for easy integration into .NET applications.

---

PR Type

Documentation

---

Description

• Add .NET client library section to README

• Link to LibreSpeed.NET repository and NuGet package

• Credit maintainer MemphiZ for the library

---

Diagram Walkthrough

flowchart LR
  README["README.md"] -- "adds .NET client section" --> SECTION[".NET Client Section"]
  SECTION -- "references" --> REPO["LibreSpeed.NET Repository"]
  SECTION -- "references" --> NUGET["NuGet Package"]
  SECTION -- "credits" --> MAINTAINER["MemphiZ Maintainer"]

Loading

File Walkthrough

	Relevant files
Documentation	README.md Add .NET client library documentation section                        README.md Added new ".NET client" section after CLI client documentation Included link to LibreSpeed.NET GitHub repository Added reference to NuGet package for easy installation Credited MemphiZ as the library maintainer +4/-0

---

[qodo-free-for-open-source-projects]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-free-for-open-source-projects]

PR Code Suggestions ✨

No code suggestions found for the PR.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Memphizzz]

Bump