Update pact-go v1 to use latest pact-ruby-standalone (ruby 3.2 + arm64 support)

[YOU54F]

as per #290 but retargeted against v1.x.x branch

---

Changes to traveling ruby to support additional platforms

Details of changes made to travelling ruby

PR's to Travelling ruby to update the supported archs

• Feat: Upgrade to Ruby 3.1.2 / Support ARM64 OSX/Linux  phusion/traveling-ruby#132
• Ruby 3.2.2 + Multi-Arch CI Builds phusion/traveling-ruby#133

Which means we can now support

OS	Ruby	Architecture	Supported
OSX	3.2.2	x86_64	✅
OSX	3.2.2	aarch64 (arm)	✅
Linux	3.2.2	x86_64	✅
Linux	3.2.2	aarch64 (arm)	✅
Windows	3.2.2	x86_64	✅
Windows	3.2.2	x86	✅
Windows	3.2.2	aarch64 (via x86 emulation)	✅

Details of changes made to pact-ruby-standalone

• Feat/ruby3 2 2 plus arm64 pact-ruby-standalone#100
• https://github.com/pact-foundation/pact-ruby-standalone/releases/tag/v2.0.1

Details of changes made to pact-go

These have been consumed in the pact-go project, and tested cross platform

In order to test ARM64 on MacOS, and Linux, I have utilised cirrus-ci, which is free for open-source usage (within reasonable limits)

OS	Standalone Version	Architecture	Tested
OSX	v2.0.3	x86_64	GitHub Actions
OSX	v2.0.3	aarch64 (arm)	Cirrus CI
Linux	v2.0.3	x86_64	GitHub Actions
Linux	v2.0.3	aarch64 (arm)	Cirrus-CI
Windows	v2.0.3	x86_64	untested
Windows	v2.0.3	aarch64 (via x86 emulation)	untested
Windows	v2.0.3	x86	untested

User facing notes

• Linux
• Adds support for arm64
• Drops support for x86 Linux
• Adds support for macos arm64
  • macOS arm64 (m1/m2) users will no require require installing rosetta
• Windows
  • i386 and x86_64 builds available

[coveralls]

coverage: 77.52%. remained the same when pulling 852836e on YOU54F:test/pact-2.0.1 into 1668622 on pact-foundation:v1.x.x.

[mefellows]

Nice! Thanks.

Looking at the commits, nothing would appear in the changelog. Is there a way to rebase and update a commit to add a feat?

In this package, I usually go for a feat: update to standalone x.y.z

[YOU54F]

np makes total sense, have done that but just yak shaving some things whilst I am here - will poss split these out into sep PR's

• golanglint-ci job failing, post v3 it requires a setup-go step
  • https://github.com/golangci/golangci-lint-action#compatibility
  • it fails on 1.18.x go version, not sure if we should run against both
• Appveyor job hasn't passed in a loooooooong time (2-3 years)
  • Happy to look at it, might be failing to connect to docker, as windows (https://docs.docker.com/desktop/networking/#i-want-to-connect-from-a-container-to-a-service-on-the-host)
• Updated Pact-broker config to use pactfoundation image over dius, and added healthcheck