Use consistent naming scheme for properties

[richlander]

Notice the inconsistent use of "enable" and to some degree "true".

<PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net8.0</TargetFramework>
    <RootNamespace>hello_dotnet</RootNamespace>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
    <InvariantGlobalization>true</InvariantGlobalization>

    <!-- Publishing properties -->
    <EnableSdkContainerSupport>true</EnableSdkContainerSupport>
    <PublishAot>true</PublishAot>
    <ContainerFamily>jammy-chiseled</ContainerFamily>
    <ContainerRepository>hello-chiseled-aot</ContainerRepository>
  </PropertyGroup>

</Project>

@baronfel

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[MiYanni]

@richlander @baronfel Don't multiple teams own different properties and how those properties are used? Trying to "heard the cats" on this feels like it would be difficult. Plus, some of these properties are set by tooling (like VS project system), so you'd have to do a lot of work to make things consistent here. The scope is potentially large and the teams/tooling involved is also potentially large, but the gain would be low/minimal and primarily from a user consistency standpoint only. MSBuild has no native way to enforce property rules so I don't know if this ask is realistic. Thoughts?