Question about NuGet/setup-nuget

[sungam3r]

I see that each CD workflow uses

  - name: setup nuget
      uses: NuGet/setup-nuget@v1.0.5
      env:
        ACTIONS_ALLOW_UNSECURE_COMMANDS: 'true'
      with:
        nuget-version: latest

After that it executes

 - name: Publish <NAME_HERE> Health Check nuget
      run: dotnet nuget push ./artifacts/AspNetCore.HealthChecks.NAME.*.nupkg -k ${{secrets.NUGET_API_KEY}} -s https://api.nuget.org/v3/index.json --skip-duplicate

but dotnet nuget push is a built-in dotnet CLI command. So why to bother with setup nuget step in all CD workflows?
ping @carlosrecuero @unaizorrilla

[sungam3r]

@carlosrecuero Also I suggest to get rid of --include-source --include-symbols in all pack commands. With embedded PDBs and SourceLink all that jumping over "debugger options" is unnecessary.