Feat/v4 asynchronous messages pact core v17

[YOU54F]

testing #1520 with #1563

[YOU54F]

@mefellows

I decided to do MatchersV3 at the same time. It felt like it made sense.

[YOU54F]

Thought it would be nice to show a usecase with multiple interactions in a single test (Pact Broker Client traverses multiple calls via HAL relations) and see what it lookss like.

It feels like it would be nice to chain an addInteraction off a willRespondWith here

[YOU54F]

note the TODO.

Having a first class way of adding a second interaction here, rather than it just working via what looks like magic :)

V4InteractionWithResponse won't allow chaining of a V4UnconfiguredInteraction.

Could addInteraction accept a configured interaction?

I assume for most parts having it for the http interactions would be suitable, or only allow chaining of similar interaction types. Haven't though too much of whether it would apply for messaging, but may need to be considered for plugin interactions.

[YOU54F]

Sample projects consuming the updated code

• grpc feat: update to PactV4 interface YOU54F/pact-workshop-grpc-js#1
• kafka async Feat/pact js v4 pact-workshop-message#86
• rest consumer Feat/pact js v4 pactflow/example-consumer#254
• rest provider Feat/pact js v4 pactflow/example-provider#137
• rest workshop https://github.com/pact-foundation/pact-workshop-js

pact-js consumers

• jest-pact feat!: change Pact to PactV2 / PactOptions to PactV2Options jest-pact#423
• nest-js-pact https://github.com/pact-foundation/nestjs-pact
• mocha-pact https://github.com/pact-foundation/mocha-pact