[Maintenance] Project File Normalization

[cschuchardt88]

Change Log

• Move common msbuild properties to Directory.Build.props.
• Fixed pathing when solution file isn't targeted for builds.
• Add new nuget source (./pkgs/ directory in the root).
• Added `./pkgs/' directory in the root.
• Added PackageOutputPath property for msbuild in Directory.Build.props files.
• Added *.target files to .gitattributes file.
• Added *.snupkg files to .gitignore file.
• Removed common properties for OutputPath, PackageId and RootNamespace from *.csproj files.
• Updated github workflow file (nuget.yml) to use ./pkgs/ directory in the root.
• Updated copyright year to 2025.

Type of change

• Optimization (the change is only an optimization)
• Style (the change is only a code style for better maintenance or standard purpose)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[Jim8y]

well,, the output path is changed again.... the name is weird cause neogo has this folder as well for another purpose.

[cschuchardt88]

This for building nuget packages. What would you like the name to be? Other than that everything else is the same. Just moved to the *.props files.

[cschuchardt88]

@shargon @Jim8y @nan01ab
You all need to download the PR's code in any PR, when you think there is an issue. Prove the issue is real, than create issue in the given PR's about it. I spend a lot of time testing and critiquing the code with a fine tooth comb. It really wastes my time and everyone else. Having to example something, if you would just download the PR and test it. If downloading the PR is a waste of time or to much for you. Now you know how I feel explaining it. Now asking a question about if something changed or what does it do. Is a good question. Also I go out of my way to fill out a detailed description. So All I ask is take some time to read the description and download PR if you think something doesn't work the way you think. Especially if the code is too complex for you to understand. Just do the research before you start issue please.