Please add support for the following keys to be used in the consumer version selectors when fetching pacts for verification:

{ "deployedOrReleased": true }

{ "deployed": true }

{ "released": true }

{ "environment": "<env name>" }

{ "consumer": "<name>" } // this may already be supported, please add it if not

These keys can be used in various combinations ( eg. `{ "env

Please add support for the following keys to be used in the consumer version selectors when fetching pacts for verification:

{ "deployedOrReleased": true }

{ "deployed": true }

{ "released": true }

{ "environment": "<env name>" }

{ "consumer": "<name>" } // this may already be supported, please add it if not

These keys can be used in various combinations ( eg. `{ "envir

Is your feature request related to a problem? Please describe.
We utilize contract tests to test our projects and rely on a passing build to signify that our project is working. However we have seen that passing contract tests is not necessarily a sure indicator of a project's status. If a contract definition is bad then the generateTests goal of the spring-cloud-contract-maven-plugin will ju

Software versions

• OS: linux
• Consumer Pact library: Pact go v1.5.3
• Provider Pact library: Pact go v1.5.3
• Golang Version: 1.15

Expected behaviour

The pact go library should allow to exactly match multiple occurrences of the same query parameter as it is supported within pact files and by libraries for other platforms as shown e.g. [here](https://docs.pact.io

❕ Problem Statement

Provide resources to help new users become proficient in Pact and PactSwift

💬 Task Description

Create an end-to-end workshop based on the canonical pact one (https://github.com/pact-foundation/pact-workshop-js).

👩‍🔧 Technical Design Notes

Suggest using the JS provider as the "backend" for the workshop, to both reduce the effort required in this workshop and