Support registration manual NuGet source to NuGet.Config

Description:
Support registration manual NuGet source to NuGet.Config

Justification:
When we uses private NuGet repository like nexus, We need to configure our source to NuGet.Config.

I'm currently using with these code, But It is too long and scattered in many workflows.

- name: Add NuGet source (Private Nexus)
  id: add-nuget-source
  run: |
    dotnet nuget remove source Nexus | true
    dotnet nuget add source ${{ secrets.PRIVATE_NUGET_SOURCE }} \
      --name Nexus \
      --username ${{ secrets.PRIVATE_AGENT_NEXUS_USERNAME }} \
      --password ${{ secrets.PRIVATE_AGENT_NEXUS_PASSWORD }} \
      --store-password-in-clear-text

Also, we need to remove this configure with these code when using ghcr.

- name: Remove NuGet source (Private Nexus)
  if: ${{ always() && steps.add-nuget-source.conclusion == 'success' }}
  run: dotnet nuget remove source Nexus | true

Are you willing to submit a PR?
Yes, I'm interested in. But I need a help.
I don't know nice way to resolve these many arguments. Some idea please

Start by reviewing the setup-dotnet action inputs and the workflow steps shown in the issue, with attention to how NuGet.Config and the dotnet nuget commands are currently handled. Done should provide a defined way to register a manual private NuGet source without repeated add/remove steps across workflows, but the input design still needs maintainer guidance.