[ASPNETCORE] Add support for central package version management

[Urganot]

This pr adds support for using centralized package version management.

For this two options were added:

1. useCentralizedPackageVersionManagement Type: Boolean, Default: false
2. centralizedPackageVersionManagementOptOut Type Boolean, Default: false

Setting useCentralizedPackageVersionManagement true will add the ManagePackageVersionsCentrally property to the csproj file, set the value to true and remove explicit versions from packages
Setting useCentralizedPackageVersionManagement true will add the ManagePackageVersionsCentrally property to the csproj file and set the value to false

Template files for both kinds of projects were updated accordingly.
A sample with useCentralizedPackageVersionManagement: true was added

Technical Committee mentions:
@mandrean @shibayan @Blackclaws @lucamazzanti @iBicha

PR checklist

• Read the contribution guidelines.
• Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• Run the following to build the project and update samples:

  ./mvnw clean package || exit
  ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
  ./bin/utils/export_docs_generators.sh || exit
  

  (For Windows users, please run the script in Git BASH)
  Commit all changed files.
  This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
  These must match the expectations made by your contribution.
  You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
  IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
• File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

[wing328]

https://github.com/OpenAPITools/openapi-generator/actions/runs/12040139303/job/33660370623?pr=20192

i don't think .net 9.0 is supported by the aspnetcore generator at the moment, and we welcome PRs with such enhancement.

[Urganot]

https://github.com/OpenAPITools/openapi-generator/actions/runs/12040139303/job/33660370623?pr=20192

i don't think .net 9.0 is supported by the aspnetcore generator at the moment, and we welcome PRs with such enhancement.

That wasn't on purpose. It was left from my changes regarding .net9. I corrected it

Btw. can I set a PR to squash merge?

[Urganot]

I noticed that the regenerated sample files are now using windows style line breaks and directory divider even in strings.

Do you know of a way to fix this?

[wing328]

pushed a commit with updated samples and docs. let's see how that goes

[wing328]

can you please review the build errors (e.g. https://github.com/OpenAPITools/openapi-generator/actions/runs/12092892132/job/33723209893?pr=20192) when you've time?

[Urganot]

Done

[Urganot]

The up to date check fails because of the window/linux thing

[wing328]

do you have Windows Subsystem for Linux (WSL) installed (assuming you're using Windows)? you can try to run the script to update the samples under WSL.

[Urganot]

Using WSL worked

[wing328]

can we simplify this to just one option (e.g. managePackageVersionsCentrally, which is a string, not boolean)?

{{#ManagePackageVersionsCentrally}}
    <ManagePackageVersionsCentrally>{{{.}}}</ManagePackageVersionsCentrally>
{{/ManagePackageVersionsCentrally}}

if it's set to false, add another additional properties skipVersion for below.

[Urganot]

If I understand you correctly that would mean when setting it to false it has a different behaviour than dont setting it at all?
Personally I dont like this. As a user I would expect that if I dont set it at all it would do the same as false. If you want to have only one option though, we could use a enum with "true", "opt-out", "default". Not setting it would use the default option

[wing328]

As a user I would expect that if I dont set it at all it would do the same as false

we can default the option to false

[Urganot]

We could, but not having the property in the .csproj file and setting the property to false are very different things

[wing328]

OK

we could use a enum with "true", "opt-out", "default". Not setting it would use the default option

what about having 3 values in a single option instead as you suggested earlier?

[wing328]

Should be automatic

[Urganot]

Could you take a look the the last commit? I cant figure out why it doesnt validate correctly

[Urganot]

I tried everything I could think of but I still cant get it to validate that the value is one of the enums. How do we procede with this pr?

[wing328]

I'll try to find time this week to address the remaining piece and then get this PR merged to move it forward.

[Urganot]

Thanks :)