Update the repository description and topics to reflect MTConnect v2.7 support

[ottobolyos]

@PatrickRitchie, the GitHub repository description currently reads:

Fully featured .NET library in C# to build MTConnect Agent, Adapter, and Client Applications. Pre-built Agents with Windows Installers. Support for Windows and Linux. Supports MTConnect Versions up to 2.5. Supports .NET Framework 4.6.1 up to .NET 9

The 'up to 2.5' line is no longer accurate. After PR #139 ('feat(common): add Version27 constant, advance Max, advertise v1.0–v2.7') landed earlier in this campaign, MTConnect.NET ships full support for v2.6 and v2.7 — every DataItem, Component, Observation, and envelope shape introduced in those two releases has a generated type, an [Introduced] / [Deprecated] stereotype pair, and a compliance regression pin under tests/Compliance/.

Would you update the description? A minimal edit:

Fully featured .NET library in C# to build MTConnect Agent, Adapter, and Client Applications. Pre-built Agents with Windows Installers. Support for Windows and Linux. Supports MTConnect Versions up to 2.7. Supports .NET Framework 4.6.1 up to .NET 9

Two small consistency wins that could land at the same time:

• The 'Topics' (tags) sidebar currently lists adapter, agent, csharp, dotnet, iiot, industry40, manufacturing, mqtt, mtconnect, trakhound, vbnet. A version-flavoured mtconnect-v2-7 (and optionally mtconnect-v2-6) topic would surface the repository in version-scoped GitHub searches once an integrator filters by it.
• The '.NET Framework 4.6.1 up to .NET 9' phrasing reads fine as is; if 'through .NET 9' feels editorially tighter, that is the only other wording tweak worth picking up.

No code change in this issue — purely a metadata edit request. The library itself already advertises v2.7 via MTConnectVersions.Max and the per-version compliance matrix; the repository description has just drifted behind the shipped surface.

[PatrickRitchie]

Thanks for the suggestion! The repo description should be updated now.