Moved custom module to a later position to override Publish-GithubRel…

[zbalkan]

…ease function

The builds fail due to a conflict of two modules have same function with different parameters. This PR is a simple attempt to change the default build script behavior.

Description

The BuildTools.psm1 module of yours is defined in the build script.

ConfluencePS/ConfluencePS.build.ps1

Line 31 in c86f787

Import-Module "$PSScriptRoot/Tools/BuildTools.psm1" -Force -ErrorAction Stop

Then BuildHelpers module is imported 3 lines later.

ConfluencePS/ConfluencePS.build.ps1

Line 34 in c86f787

Import-Module BuildHelpers -Force -ErrorAction Stop

However they both have the same command, Publish-GithubRelease with different parameters. The first one, your custom module requires a parameter called GITHUB_ACCESS_TOKEN while the latter requires AccessToken as you can see here. And the second one is imported later with -Force parameter, it overrides the function from the first module. It is better to make a decision:

• Keep both functions but move custom module a few lines below to override external one.
• Remove Publish-GithubRelease from BuildTools.psm1 and use the one from BuildHelpers module.

This PR picks the first option.

NB! I did not have the means to test your pipeline so the change also can create newer conflicts.

Motivation and Context

closes (#200)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My code follows the code style of this project.
• I have added Pester Tests that describe what my changes should do.
• I have updated the documentation accordingly.