Gauge Confluence v0.10.4

• #34 - Remove debugging output from console

Gauge Confluence v0.10.3

• #33 - Fix message in helper script

Gauge Confluence v0.10.2

• #31 - Fix bug when republishing after aborted attempt

Gauge Confluence v0.10.1

• #29 - Add helper script to print space pages

Gauge Confluence v0.10.0

Do not publish if first time & Space is not empty (#28)

* Allow "tidy" as first word of git commit messages

This doesn't affect the Confluence plugin in any way, it's just a change
to the [opinionated git commit message checker][1] we use to ensure
[good commit messages][2].

[1]: https://github.com/mristin/opinionated-commit-message
[2]: https://chris.beams.io/posts/git-commit/

* Tidy specification wording

* Do not publish if first time & Space is not empty

The Space can have a homepage but no other pages before the first ever
publish to the Space.  Having the Space only ever contain published
Gauge specs ensures that there is no danger of the plugin inadvertently
overwriting or deleting manually created Confluence pages.

* Bump plugin minor version

Gauge Confluence v0.9.1

• #23 - Fix typo in helper script

Gauge Confluence v0.9.0

• #22 - Delete existing published specs before publishing

Gauge Confluence v0.8.0

Do not publish directories with no specs (#21)

* Do not publish directories with no specs

This commit ensures that any directories without any specs in them are
not published to Confluence.  Prior to this commit these directories
were being published, appearing in Confluence as pages without any
content or subpages. This was distracting when trying to browse the
published specs in Confluence.

One example of this manifesting itself prior to this commit was if the
Gauge [concept files][1] were put into their own concepts directory.
As we only publish specs and not concepts to Confluence, having concepts
in their own directory was leading to empty directory pages being
published prior to this commit.

The functional tests implementation code in this commit was lifted and
shifted with only minor alterations from [the functional tests repo for
core Gauge][2] (just like the existing functional test implementation
code) - no point in reinventing the wheel.

One other noteworthy thing is that the code to delete a page uses the
low level [Go net http client][3], rather than the higher level
[confluence-go-api client][4]. This is because there was a subtle bug
with the confluence-go-api client (it was returning an error even after
a successful delete, despite returning [the correct 204 status
code][5]). It may be worth removing the confluence-go-api client
altogether in a future pull request, as [minimising dependencies is
generally a good thing][6].

[1]: https://docs.gauge.org/writing-specifications.html#concepts
[2]: https://github.com/getgauge/gauge-tests
[3]: https://pkg.go.dev/net/http
[4]: https://github.com/Virtomize/confluence-go-api
[5]: https://developer.atlassian.com/server/confluence/confluence-rest-api-examples/#delete-a-page
[6]: https://endjin.com/blog/2018/09/whose-package-is-it-anyway-why-its-important-to-minimise-dependencies-in-your-solutions

* Remove unused import

* Exclude long urls in comments from go linting

As per:
https://github.com/golangci/golangci-lint/issues/207#issuecomment-534771981

* Bump plugin minor version

Gauge Confluence v0.7.4

• #20 - Ensure test Confluence spaces have unique keys

Gauge Confluence v0.7.3

• #19 - Add debug logging to diagnose date time parsing