⬆️ Bump files with dotnet-file sync

Use Project for default launch profile command name

Ensure the project-name entry written to Properties\\launchSettings.json uses the fixed commandName value expected by launch profiles instead of the MSBuild project name.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Add default project launch profile

Ensure generated launchSettings.json includes Visual Studio's default project-named profile alongside SmallSharp file profiles.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

+Mᐁ includes

Ensure properties are always set in props+targets

This prevents a scenario where the .NET SDK props don't get a key property early enough (i.e. TargetFramework) from the script and uses the one in the .csproj which was intended to be overriden.

+Mᐁ includes

Ensure when running from VS, output supports UTF-8

The console started by VS (even if it's the terminal one) by default does not seem to be set up to support UTF-8. To be on the conservative side, we just set up the encoding in DEBUG builds so things Just Work from VS by default.

This problem doesn't exist when running from a regular terminal.

Update SmallSharp SDK version in README

⬆️ Bump files with dotnet-file sync

Add blank sample with only implicit usings