chore(examples):- show matchers in use on consumer/provider side for MessagePact

[YOU54F]

Updates to #313

Adds examples relating to answer here in original raised issue #308 (comment)

[YOU54F]

Hey @JP-Ellis

Although this PR won't be able to be merged now, it would still be useful to show matchers being used in the message examples and having a test to cover them.

Might be something to consider adding in to the refactored suite.

Happy for this to be closed, if its tracked somewhere 👍🏾

[JP-Ellis]

Do you think this would be covered as part of implementing the compatibility suites in:

• Implement HTTP consumer compatibility suite #420
• Implement HTTP provider compatibility suite #421

I would definitely make use of the work in this PR so that it isn't wasted.

[YOU54F]

I reckon the following would be more apt for message pact 👍🏾

• Add support and example for a message consumer test using Rust engine #380
• Add support and example for verifying a message provider using the Rust engine #379

The main point here is the user has to call matchers.get_generated_values to reify the message (strip it of matchers) before passing it to the handler. Other languages such as pact-js call the reify method under the hood so the user doesn't need to worry about the implementation detail.

https://github.com/pact-foundation/pact-js/blob/768b70e4305669e71700a275ff4204f573788a7e/src/messageConsumerPact.ts#L193