migrate Commander API to .NET 10

[savaladaojr]

What changed

Migrated Commander API from ASP.NET Core 3.1 to .NET 10 LTS, updated the project hosting model to Program.cs, refreshed the main NuGet packages, and aligned the README plus requirements doc with the current architecture.

Why

The previous stack was out of support. This update moves the application onto a supported .NET LTS release while preserving the existing REST API surface.

Validation

• dotnet build
• dotnet list package --outdated
• dotnet test --no-build
• dotnet ef migrations list --no-build

Notes

• Startup.cs was removed in favor of the modern hosting model.
• CommandReadDto now returns platform.
• The local connection string no longer stores explicit username/password values in the repository.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e37e0acf5e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Use a valid partial Program declaration

This migration leaves Program.cs with public partial class Program;, but C# class declarations still require a body, so the project will not compile as soon as this file is built. If the intent is to expose Commander.Program for tests or EF tooling, declare it with an empty body such as public partial class Program { }.

Useful? React with 👍 / 👎.