[ISSUE]: Add support for specifying a custom nuget.config file for tool installation in gitversion-setup

[dmarty-ctc]

Prerequisites

• I have written a descriptive issue title
• I have searched issues to ensure it has not already been reported

GitVersion package

AzureDevops task

What are you seeing?

Currently, the gitversion-setup task installs the GitVersion .NET tool directly from nuget.org without a way to override the feed source.
As a result, the setup step fails in environments where outbound connections to public package feeds are blocked.

In our enterprise environments, self-hosted Azure DevOps agents are not allowed to connect to public feeds like nuget.org. Instead, private Azure Artifacts feeds or Artifactory feeds are used with upstream sources for internal dependency management.

What is expected?

Introduce a new optional input parameter to the gitversion-setup task:

• task: gitversion-setup@4
  inputs:
  versionSpec: '6.4.x'
  nugetConfigPath: '$(Build.SourcesDirectory)/nuget.config'

Steps to Reproduce

Currently, the only workaround is to preinstall the GitVersion.Tool on all agents or to run a custom script which installs the tool.

Output log or link to your CI build (if appropriate).

[gittools-bot]

🎉 This issue has been resolved in version v4.2.0 🎉
The release is available on:

• GitHub Release

Your GitReleaseManager bot 📦🚀