Update repository to latest versions and rebrand from FLINK.NET to FlinkDotnet

[Copilot]

This PR comprehensively updates the entire repository to the latest available versions and completes the rebranding from "FLINK.NET" to "FlinkDotnet" as requested in the issue.

Version Updates

SDK and Tools:

• .NET SDK: Updated from 8.0.117 to 8.0.118 (latest available)
• SonarAnalyzer.CSharp: Updated from 10.11.0.117924 to 10.15.0.120848 (latest)

NuGet Packages:

• System.Text.Json: 8.0.5 → 8.0.6
• Confluent.Kafka: 2.5.3 → 2.11.0 (unified across all projects)
• Microsoft.AspNetCore.OpenApi: 8.0.0 → 8.0.18
• Swashbuckle.AspNetCore: 6.4.0 → 9.0.3
• Microsoft.Extensions.Hosting: 8.0.0 → 8.0.1

Branding Changes

Repository References:

• Updated all GitHub repository URLs from github.com/devstress/FLINK.NET to github.com/devstress/FlinkDotnet
• Changed project authors from "FLINK.NET Team" to "FlinkDotnet Team"

Documentation Updates:

• README.md: Replaced all "Flink.NET" references with "FlinkDotnet" throughout the main documentation
• Getting Started Guide: Updated title and clone URLs to reflect new repository name
• Coverage Documentation: Updated technical documentation to use consistent FlinkDotnet branding

Code Quality Improvements

The updated SonarAnalyzer detected and helped fix a code quality issue:

• S3267 Issue Fixed: Simplified a foreach loop in MultiTierRateLimiter.cs using LINQ's All() method instead of manual iteration

// Before
foreach (var tier in _tiers.Skip(1)) {
    if (!ValidateTierHierarchy(tier))
        return false;
}
return true;

// After
return _tiers.Skip(1).All(ValidateTierHierarchy);

Compatibility & Testing

• Build Verification: All projects build successfully with zero warnings or errors
• Package Conflicts Resolved: Fixed version conflicts between main projects and sample projects
• No Breaking Changes: All existing functionality preserved during updates
• Cross-Platform Compatibility: Maintained compatibility across all supported platforms

All changes maintain backward compatibility while bringing the repository up to the latest standards with consistent branding throughout.

Fixes #4.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.