Remove buildserver output argument from GitVersion tool as it's duplicating the actions behavior

[arturcic]

Removed the '/output buildserver' argument from the gitversion tool execution. Updated all related unit tests to reflect this change, ensuring consistency and correctness across different configurations.

[mergify]

Thank you @arturcic for your contribution!

[gittools-bot]

🎉 This issue has been resolved in version v3.0.4 🎉
The release is available on:

• GitHub Release

Your GitReleaseManager bot 📦🚀

[WilliBarankin]

Looks like this change completely brakes Azure pipeline. Rolling back to version 3.0.3 fix the issue

[Nidolai]

Brakes Azure pipelines for me as well.

[davidkeaveny]

I'm using the Azure DevOps GitVersion task, and this change from 3.0.3 to 3.0.4 has broken my pipelines, as it's not now setting $(Build.BuildNumber) - what setting do I need to update to restore normal functionality?

If my pipeline YAML includes the following:

stages:
- stage: Packaging
  jobs:
  - job: buildAndPackage
    steps:
    - checkout: self
      fetchDepth: '0'
    - task: gitversion/setup@3
      inputs:
        versionSpec: '5.10.x'
    - task: gitversion/execute@3
      inputs:
        useConfigFile: true
        configFilePath: 'GitVersion.yml'

Previous builds, which picked up v3.0.3 would produce the following output:

GitVersion executed successfully
Async Command Start: Update Build Number
Update build number to 1.15.0-unstable.90 for build 125299
Async Command End: Update Build Number
Finishing: Calculate version number

But today's builds, picking up v3.0.4, produce the following output:

GitVersion executed successfully
Finishing: Calculate version number

I can work around this by explicitly setting the GitVersion tool number in my pipeline YAML to v3.0.3, then my builds pass again, so it's definitely the v3.0.4 build that is breaking things for me.

[arturcic]

@davidkeaveny that's a valid bug, I will fix it as part of the #1389